Tabula Mcp

io.github.tradetabulaPublished by GitHub account tradetabulav0.1.0Updated Nov 4, 2026

Credit for AI agents: pay x402 sellers from a credit line, repay with one signature and no ETH

The publisher's own server: Tabula MCP

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Local MCP server that gives an AI agent a credit line on Tabula so it can pay x402 sellers and repay without holding ETH.

What you can do
No tool list is published, so capabilities are inferred from the configuration. The server connects an agent to Tabula's gateway on Robinhood Chain or Base, where the agent can draw on a credit line to pay x402 sellers. It signs and repays on the agent's behalf, with repayment described as a single signature and no ETH required. It can run with autopay enabled, and it reads the chain's RPC to check what it signs. It can also operate through a sub-agent key that only pays and reads.
When to use it
Use it when an agent needs to buy from x402-priced services and you want spending backed by a credit line rather than a pre-funded wallet. It suits setups on Robinhood Chain or Base where the agent already has an ERC-8004 identity or a Tabula sub-agent key.
Requirements
Runs locally over stdio as the npm package tabula-mcp, so Node.js is needed. Requires TABULA_GATEWAY_URL, plus either TABULA_AGENT_ID with TABULA_AGENT_KEY, or TABULA_SUBKEY. Optional: TABULA_RPC_URL, TABULA_AUTOPAY, and contract addresses for unknown deployments. Network access to the gateway and chain RPC.
Before you install
TABULA_AGENT_KEY is a private key that owns the agent's identity, and TABULA_SUBKEY is a paying sub-agent key; both are secrets. The server signs transactions and spends credit, and TABULA_AUTOPAY can start with autopay on, so spending may occur without a prompt. It contacts Tabula's gateway and an RPC endpoint. Review limits before enabling.

Installation

In SourceWeft

  1. Open Tabula Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tabula integrations