tabula-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TABULA_LEDGER | No | The ledger contract address, for a deployment the server does not already know. | |
| TABULA_SUBKEY | No | A sub-agent's key, used instead of TABULA_AGENT_ID and TABULA_AGENT_KEY. | |
| TABULA_AUTOPAY | No | Set to on to start with autopay on. | |
| TABULA_RPC_URL | No | The chain's RPC URL, which the owner's server reads to check what it signs. The public RPC is used by default. | |
| TABULA_AGENT_ID | No | The agent's ERC-8004 id. | |
| TABULA_BOND_ZAP | No | The bond zap contract address, for a deployment the server does not already know. | |
| TABULA_AGENT_KEY | No | The key that owns the ERC-8004 identity. | |
| TABULA_GATEWAY_URL | Yes | Tabula's gateway: https://api.tabula.credit for Robinhood Chain, https://api-base.tabula.credit for Base. Must be https, or http to this machine only. | |
| TABULA_BATCH_REPAYER | No | The batch repayer contract address, for a deployment the server does not already know. |
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 |
|---|---|
| credit_statusB | Your Tabula credit line: limit, open tab, what you owe and when it is due. |
| pay_with_creditA | Pay for an x402 (HTTP 402) resource from your credit line. Tabula pays the seller now; the charge goes on your tab, which you repay later. |
| list_sellersA | Sellers you can pay on credit, with prices. A featured seller paid for its place in this list. |
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 3 tools
Each tool has a clearly distinct role: checking credit status, paying via credit, and listing available sellers. There is no meaningful overlap between them, so an agent can select the right tool without confusion.
The names use three different structures: noun_noun (credit_status), verb_preposition_noun (pay_with_credit), and verb_noun (list_sellers). They remain readable, but the mixed conventions prevent a predictable pattern.
Three tools is a reasonable minimal surface for a focused credit-payment server. It is slightly thin, but each tool earns its place and the scope is coherent.
The surface supports checking credit, listing sellers, and making a credit payment, but there is no tool to repay or settle the tab despite descriptions saying the charge is repaid later. This creates a significant lifecycle gap and a likely dead end for agents.