Local stdio MCP server bridging any MCP client to Pink Agentic AI Payments remote MCP (sandbox preview, test money)
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Topics declared
- ✓Documented (README)
claude mcp add pink-agentic-payments-mcp -- npx -y pink-agentic-payments-mcp{
"mcpServers": {
"pink-agentic-payments-mcp": {
"command": "npx",
"args": ["-y", "pink-agentic-payments-mcp"]
}
}
}MCP Servers overview
# pink-agentic-payments-mcp
Pink Agentic AI Payments checks every payment an agent requests against company spending rules (budgets, payee allow-lists, human approval) before any payment credential is issued.
This package is a local **stdio** MCP server that bridges any MCP client (Claude Desktop, Cursor, VS Code, Windsurf, n8n's MCP client, and others) to Pink's remote Streamable HTTP MCP server. It forwards `tools/list` and `tools/call` (and resources/prompts, if the remote adds them) transparently, so the local server always reflects whatever tools Pink's remote server currently exposes — nothing is hardcoded.
Sandbox preview: test money only, no signup required to get a key.
## Quick start
### 1. Get a free sandbox agent key
No signup needed. Either run:
```bash
npx -y pink-agentic-payments-mcp --create-sandbox
```
which creates a sandbox workspace and prints a ready-to-paste client config, or create one yourself:
```bash
curl -s -X POST https://agentic-sandbox.pinkwallet.com/v1/sandbox/workspaces
```
and take any `agents[].key` from the response.
### 2. Add it to your MCP client
**Claude Desktop** (`claude_desktop_config.json`), **Cursor**, **Windsurf**, and most other stdio-based MCP clients:
```json
{
"mcpServers": {
"pink": {
"command": "npx",
"args": ["-y", "pink-agentic-payments-mcp"],
"env": { "PINK_AGENT_API_KEY": "pk_sandbox_agent_..." }
}
}
}
```
**VS Code** (`.vscode/mcp.json`):
```json
{
"servers": {
"pink": {
"command": "npx",
"args": ["-y", "pink-agentic-payments-mcp"],
"env": { "PINK_AGENT_API_KEY": "${input:pink_agent_key}" }
}
}
}
```
Env vars:
- `PINK_AGENT_API_KEY` (required) — your agent key from a sandbox workspace.
- `PINK_MCP_URL` (optional) — defaults to `https://agentic-sandbox.pinkwallet.com/mcp`.
## Tools
These are live from the remote server's `tools/list` response (see [`TEST-OUTPUT.txt`](./TEST-OUTPUT.txt) for the full run):
| Tool | What it does |
| --- | --- |
| `pink.get_budget` | What this agent may still spend: monthly budget left, spent today, single-payment cap, vault balances, company daily ceiling. |
| `pink.list_payees` | Suppliers, platforms and contractors this company has approved. Paying anyone else stops and asks a person. |
| `pink.list_rules` | The policy rules that apply to this agent, in evaluation order. First match decides: allow, ask, or block. |
| `pink.check_policy` | Dry run. Returns `would_allow` / `would_ask` / `would_block` with the rule and full decision trace. Nothing is spent or held. |
| `pink.request_payment` | The real call. Returns `allowed` with a single-use credential, `pending_human` with a `hold_id` while a person is asked, or `blocked` with the reason. |
| `pink.get_credential` | Poll a pending hold. Once a person approves, this returns the credential. |
| `pink.report_receipt` | File the receipt for a completed payment so it reconciles. |
## How this was tested
`TEST-OUTPUT.txt` in this repo is the full, unedited output of three real runs against a live sandbox workspace (test money only):
1. The built server (`dist/bin.js`) driven over stdio by an MCP SDK test client — `tools/list` plus `pink.request_payment` calls that returned real `allowed` (with an issued sandbox credential), `blocked` (over monthly budget), and `pending_human` (new-payee approval) decisions.
2. The official MCP Inspector CLI (`npx @modelcontextprotocol/inspector --cli`) run headless against the same built server.
3. The same stdio test run again from a packed tarball (`npm pack` then `npx -y ./pink-agentic-payments-mcp-0.1.0.tgz`) in a clean directory, to prove the `npx` install path works end to end.
## Links
- Docs hub: [pinkwallet.com/agentic/developers](https://pinkwallet.com/agentic/developers/)
- MCP connection guide: [pinkwallet.com/agentic/developers/connect-via-mcp](https://pinkwallet.com/agentic/developers/connect-via-mcp/)
- JS/TS client: [pink-agentic-payments](https://github.com/Pink-Agentic-Payments/pink-agentic-payments-js)
## Status
Sandbox preview (test money only). Published on npm as [`pink-agentic-payments-mcp`](https://www.npmjs.com/package/pink-agentic-payments-mcp) — `npx -y pink-agentic-payments-mcp` is all you need, no clone or build step required.
## License
MIT
What people ask about pink-agentic-payments-mcp
What is Pink-Agentic-Payments/pink-agentic-payments-mcp?
+
Pink-Agentic-Payments/pink-agentic-payments-mcp is mcp servers for the Claude AI ecosystem. Local stdio MCP server bridging any MCP client to Pink Agentic AI Payments remote MCP (sandbox preview, test money) It has 0 GitHub stars and its last recorded update is dated 2026-10-12.
How do I install pink-agentic-payments-mcp?
+
You can install pink-agentic-payments-mcp by cloning the repository (https://github.com/Pink-Agentic-Payments/pink-agentic-payments-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is Pink-Agentic-Payments/pink-agentic-payments-mcp safe to use?
+
Our security agent has analyzed Pink-Agentic-Payments/pink-agentic-payments-mcp and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.
Who maintains Pink-Agentic-Payments/pink-agentic-payments-mcp?
+
Pink-Agentic-Payments/pink-agentic-payments-mcp is maintained by Pink-Agentic-Payments. The last recorded GitHub activity is dated 2026-10-12, with 0 open issues.
Are there alternatives to pink-agentic-payments-mcp?
+
Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.
Deploy pink-agentic-payments-mcp to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](https://claudewave.com/repo/pink-agentic-payments-pink-agentic-payments-mcp)<a href="https://claudewave.com/repo/pink-agentic-payments-pink-agentic-payments-mcp"><img src="https://claudewave.com/api/badge/pink-agentic-payments-pink-agentic-payments-mcp" alt="Featured on ClaudeWave: Pink-Agentic-Payments/pink-agentic-payments-mcp" width="320" height="64" /></a>More MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Reverse engineer anything with agents, from app behavior down to native binaries.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev