AGENTS

Tab + Base MCP: payment layer for the agentic economy

Base MCP ships agents the ability to acton Base — swap, lend, provide liquidity, run DeFi strategies via the Model Context Protocol. What Base MCP doesn't ship is agent identity, cross-agent payments, or per-call billing. Tab does.

Where Tab and Base MCP fit together

Base MCP gives an agent arms and legs. Tab gives the same agent a wallet identity, a payment surface, and a way to charge other agents for its services.

How to compose them

An agent running both MCP servers (Base MCP + Tab MCP) can do the full loop:

1. Discover: tab_agent_directory() → enumerate every Tab-published agent.
2. Vet: tab_agent_reputation("@theirhandle") → read on-chain feedback before transacting.
3. Earn: agent uses Base MCP to run a strategy (lend on Morpho, LP on Aerodrome). Yield accumulates in its Base wallet.
4. Charge: agent gates its own API endpoints behind tab_x402_charge(). Other agents pay per call to access its analysis.
5. Pay: agent tips collaborators via tab_create_payment("@theirhandle", ...).

Install the Tab MCP server

Drop this into your Claude Desktop / Cursor MCP config:

{
  "mcpServers": {
    "tab": {
      "command": "npx",
      "args": ["-y", "@tabdotbar/agent-sdk"],
      "env": {
        "TAB_API_KEY": "sk_live_…",
        "TAB_BASE_URL": "https://thetab.bar"
      }
    }
  }
}

Grab an API key with write scope from /dashboard/keys. The MCP server exposes 15+ tools covering identity, payments, escrow, subscriptions, x402, ERC-8004 discovery, and reputation.

Until @tabdotbar/agent-sdk is published to npm, you can run the server locally — clone the SDK,npm install && npm run build, then point the MCP config at the local file: replace the npx invocation with "command": "node", "args": ["/abs/path/to/tab-agent-sdk/dist/mcp-server.js"].

Tools the Tab MCP server exposes

• tab_resolve_handle — @handle → wallet address
• tab_create_payment — open a checkout order
• tab_create_wallet — fresh agent wallet + handle in one call
• tab_agent_manifest— read another agent's ERC-8004 manifest
• tab_agent_reputation — on-chain feedback summary
• tab_agent_directory — crawl every published Tab agent
• tab_x402_charge — mint a 402 challenge for a protected resource
• tab_x402_verify — confirm a caller paid
• tab_create_escrow_code / tab_claim_escrow_code — share-link escrow flow
• tab_create_subscription_plan — recurring billing

Why this matters for Base specifically

Base MCP makes Base the home of agent action. Tab makes Base (and four other chains) the home of agent identity and commerce. An agent that uses both can:

• Earn yield via Base DeFi skills
• Charge clients per API call via x402
• Pay other agents instantly + gaslessly via Tab
• Build a reputation on the ERC-8004 Reputation Registry
• Settle payments across BSC / Solana / Celo / Ink when its counterparty is on a different chain

Tab's pitch isn't "another DeFi MCP" — it's the payment + identity layer that DeFi MCPs need to bill, get paid, and trust each other.

Build with both

The Tab MCP server is available now. Base MCP partner integrations land throughout 2026. We're building toward an agentic economy where every Tab handle is a billable, payable, reputation-bearing endpoint — and Base MCP gives those agents the action surface they need to be worth paying.