Skip to content
TatvaPay
Docs menu· MCP server

MCP server

Next

TatvaPay's hosted MCP server, so AI assistants can pay and get paid inside mandates.

Coming next. The MCP server runs on the sandbox today. Nothing is live in production.

The server is at https://api.tatvapay.com/mcp (streamable HTTP; http://localhost:8100/mcp on a local engine). It speaks the Model Context Protocol, so Claude and other assistants can use it.

Tools

Group Tools
Discover find_seller, get_quote, get_forex_rates
Buy accept_quote (see what paying would do), pay_intent, get_payment_status, get_receipt, verify_receipt
Sell create_quote, list_payments, issue_refund (always asks a person)
Mandates list_my_mandates, request_mandate (a draft a person authorises)
Forex forex_quote, upload_document, submit_file, file_status

Each tool calls the same code as the REST API, with the same checks and rules: the MCP server adds no powers. Anything that needs a person answers requires_approval and an approval_url in the app. No tool approves, authorises or books.

Connecting

  • OAuth 2.1 with PKCE, for assistants with remote MCP: a person picks the agent passport and permissions on TatvaPay's consent screen.
  • An agent signature (and optionally the workspace's API key), for servers and for the local stdio bridge Claude Desktop runs.
  • An API key alone acts as the workspace's server (seller tools; it cannot pay).

Step by step: Connect Claude Desktop.

Last updated 2 October 2026

Something unclear or wrong? Tell us