Tillpad

Tillpad MCP

Everything your AI agents need to do their jobs, with a spending cap they can't go over.

Tillpad gives agents namespaced key-value storage, file upload + semantic search, receive-only email inboxes, budget-aware metering, and run keys that wipe with a signed receipt when the job is done.

Live endpoint: https://tillpad.dev/mcp

The previous endpoint https://tillpad.cnrcode.com/mcp keeps serving the same server, so existing client configs keep working.

This repository is the public catalog and schema stub for directory crawlers. It is not the hosted server. Point MCP clients at the live URL above with a Tillpad API key. Running the TypeScript in this repo does not store or search anything.

Agent guide: see AGENTS.md for discovery URLs, auth, and MCP connect snippets.

Get an API key

Zero-human (agents)

1. POST https://tillpad.dev/api/agents/bootstrap with { "email": "agent@example.com" } → bootstrapToken (no outbound mail).
2. POST https://tillpad.dev/api/billing/machine-pay with Authorization: Bearer and optional { "sku": "pro_prepaid_30d" }.
3. Settle Stripe MPP ($9.00 / 30 days) → response includes secret (tp_…) and planPeriodEnd.

See scratchpad.txt and llms-full.txt. Legal: Terms.

Human path

1. Open tillpad.dev and create an account.
2. Subscribe to Tillpad Pro on Pricing, then mint an API key in the dashboard. Secrets start with tp_.
3. Use an account key for ongoing access, or a run key when the job should expire and wipe.

Never commit a real key. Use the tp_… placeholder in configs.

Connect a client

Transport is Streamable HTTP. Send Authorization: Bearer tp_… on every request.

Cursor

Install via Cursor Marketplace (plugin)

This repo includes a Cursor plugin manifest and root mcp.json for one-click install from the Cursor Marketplace.

Tillpad MCP tools cover namespaced KVP, RAG search, receive-only email inboxes, scheduled HTTPS jobs, budget metering, and run-key wipe receipts.

1. Install the Tillpad plugin from the marketplace (or test locally — see below).
2. Open Cursor Settings → Customize → Tillpad and set Tillpad API key (tp_… from bootstrap + machine-pay or the dashboard).
3. Reload the window. MCP tools should appear under the Tillpad server.

The plugin points at https://tillpad.dev/mcp with Authorization: Bearer ${TILLPAD_API_KEY}. Never commit a real key.

Local plugin test (before marketplace submission):

# Copy catalog repo into Cursor local plugins folder

$dest = "$env:USERPROFILE\.cursor\plugins\local\tillpad" New-Item -ItemType Directory -Force -Path $dest | Out-Null Copy-Item -Recurse -Force "C:\dev\tillpad\tillpad-mcp\*" $dest

Then: Cursor Customize → Tillpad → set TILLPAD_API_KEY → Developer: Reload Window

Submit the public repo at cursor.com/marketplace/publish when ready.

Manual MCP config

User or project MCP config:

{

"mcpServers": { "tillpad": { "url": "https://tillpad.dev/mcp", "headers": { "Authorization": "Bearer tp_…" } } } }

Claude Desktop / Claude Code

{

"mcpServers": { "tillpad": { "command": "npx", "args": ["mcp-remote", "https://tillpad.dev/mcp", "--header", "Authorization: Bearer tp_…"] } } }

Generic remote MCP

{

"url": "https://tillpad.dev/mcp", "headers": { "Authorization": "Bearer tp_…" } }

Discovery manifests on the product host:

• /.well-known/mcp.json
• /.well-known/mcp/server.json
• /llms.txt

Tools

Schemas in src/server.ts match the hosted server.

Typical agent loop

1. Mint a run key with create_api_key (or the dashboard): dedicated namespace, TTL, optional op budget.
2. Store working state with manage_memory / manage_kv and/or index_document.
3. Retrieve with manage_memory / manage_kv and search_documents.
4. Call finish_run to wipe run namespaces and keep the signed receipt.

Use estimate_usage before large index jobs. get_usage shows what is left in the period.

Auth and errors

• 401 — missing or invalid Authorization: Bearer tp_…
• 402 / 429 — plan or quota. JSON includes code, status, actions, and budget
• actions[].type: "checkout" — hosted Stripe Checkout URL for a recurring human subscription
• actions[].type: "machine_pay" — agent prepaid Pro (30/90 days) or top-up SKUs via Stripe MPP; default sku pro_prepaid_30d at $9.00

This is Stripe Machine Payments Protocol, not ChatGPT Instant Checkout / ACP.

Product docs

• App: tillpad.dev
• Docs: tillpad.dev/docs
• Scratchpad: tillpad.dev/docs/scratchpad
• OpenAPI: tillpad.dev/openapi.json

The Tillpad product (Worker, billing, storage) is closed source. This catalog is MIT-licensed so directories can list tools and install snippets.

Directory listing

Registry name: `com.cnrcode/tillpad` (domain namespace via cnrcode.com).

1. Ensure https://cnrcode.com/.well-known/mcp-registry-auth is deployed (cnrcode-site repo).
2. Set GitHub repo secret `MCP_PRIVATE_KEY` (hex; see cnrcode-site key generation script).
3. Push a version tag so GitHub Actions publishes server.json to the official MCP Registry:

   git tag v0.2.0

git push origin v0.2.0

1. Optionally submit https://github.com/CNR-Consulting/tillpad-mcp at mcp.directory/submit.

Glama

This repo includes a stdio catalog stub (src/main.ts) so Glama can build a container, start the process, and introspect the 18 tool definitions. It does not implement storage or billing — clients still connect to the hosted endpoint above.

Listing: glama.ai/mcp/servers/number1101/tillpad-mcp

After claiming via glama.json, configure the Dockerfile admin page:

Glama generates its own Dockerfile from that form; the repo Dockerfile is for local smoke tests only.

Score badge (for awesome-mcp-servers and similar lists):

[![number1101/tillpad-mcp MCP server](https://glama.ai/mcp/servers/number1101/tillpad-mcp/badges/score.svg)](https://glama.ai/mcp/servers/number1101/tillpad-mcp)

Local verify:

npm ci && npm run build && npm start   # hangs on stdio — expected

docker build -t tillpad-mcp-stub . && docker run -i tillpad-mcp-stub

Full step-by-step (claim, admin Dockerfile, release, awesome-mcp PR): docs/glama-release.md.

License

MIT — catalog, documentation, and schema stub only.