tillpad-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TILLPAD_API_KEY | Yes | Your Tillpad API key (starts with tp_). Used to authenticate to the hosted Tillpad MCP server. Obtain one via the dashboard or the agent bootstrap + machine-pay flow. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| usage_getA | Get current period usage and quotas for the authenticated account |
| budget_getB | Get remaining quotas, soft thresholds, and checkout URL for topping up |
| budget_estimateA | Estimate whether an operation would hit 402/429 before spending. For rag_index you can pass textLength/byteLength instead of amount. |
| billing_machine_payA | Describe how to unlock Pro or purchase agent SKUs via Stripe MPP. Optional sku (default pro_prepaid_30d). Returns POST URL and amount; agent must call HTTP with MPP Payment credential. |
| agent_bootstrapA | Start zero-human onboarding: create bootstrap token from email (no outbound mail). Next POST /api/billing/machine-pay with Bearer bootstrapToken. |
| keys_createA | Mint a run or sub API key from an account key (REST POST /api/keys). Requires account tp_ key. |
| kvp_putB | Store a string value under a namespace/key. Response includes budget remaining. |
| kvp_getC | Read a value from namespaced KVP storage |
| kvp_deleteC | Delete a KVP key |
| kvp_listC | List keys in a KVP namespace |
| file_uploadC | Upload a UTF-8 text document for RAG indexing into a namespace. PrefLights rag_index capacity. |
| files_listC | List uploaded files (optionally filter by namespace) |
| files_typesA | List supported RAG upload file types (extensions, MIME types, extract notes) |
| rag_searchC | Semantic search over indexed documents |
| inspect_storageB | Summarize namespaces, key counts, file/vector inventory |
| run_finishA | Wipe all namespaces bound to this run key and return a signed wipe receipt. Only valid for run keys. |
| support_contactA | Contact Tillpad support from a Pro account. Delivers your subject and message to the Tillpad team; replies go to the account email. Requires an active Pro subscription. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct operation within its area—billing, keys, KVP, files/RAG, support—and the descriptions clarify boundaries. usage_get and budget_get both report quota state but with different focuses, and inspect_storage aggregates rather than duplicating the CRUD tools. Overall, misselection risk is low.
Names mix verb-first styles (usage_get, file_upload, inspect_storage) with noun-first styles (keys_create, kvp_put, run_finish) and compound nouns like billing_machine_pay. There is no consistent verb_noun convention, though prefixes like kvp_ and files_ provide some structure.
17 tools is at the high end for a single MCP server and spans several unrelated domains: billing, key management, key-value storage, RAG files, and support. For a multi-purpose platform API the count is defensible, but it is heavier than a focused, well-scoped server should be.
KVP storage has full CRUD and RAG covers upload, listing, and semantic search, but file deletion is missing and key management only supports creation, not listing or revocation. Billing covers usage and budgets but not detailed subscription state or payment history. These gaps are workable but notable for a platform toolkit.