Integrate

MCP for agents

Reviewed 20 Oct 2026·2 min

Expose TilcAI payments to an MCP client. The stdio server talks to the API; the wallet signs outside TilcAI MCP.

tilcai-mcp · v0.2.0 · Node.js ≥ 22.16 · README

Configure the client

mcp.json

{
  "mcpServers": {
    "tilcai": {
      "command": "npx",
      "args": ["-y", "tilcai-mcp@0.2.0"],
      "env": {
        "TILCAI_API_URL": "https://YOUR_INSTANCE",
        "TILCAI_NETWORK": "testnet"
      }
    }
  }
}

Inject TILCAI_API_KEY through your client's secret manager or environment, using its supported format. Do not include the real key in a shared file. Refer to your client's documentation for variable interpolation.

Available tools

MCP
Tool	Purpose
`tilcai_status`	Health, environment and routes; use this first.
`tilcai_quote`	USDC quote and recipient preflight for Stellar.
`tilcai_create_payment`	Creates the attempt and returns what the wallet must sign.
`tilcai_submit_authorization`	Submits the gasless signature to the API.
`tilcai_submit_burn`	Records the external-mode transaction hash.
`tilcai_payment_status`	Reads and reconciles up to SETTLED.

The wallet boundary

The EVM wallet, for example evm-mcp-server, signs EIP-712. TilcAI MCP does not receive private keys. The current version selects Avalanche Fuji → Stellar Testnet or C-Chain → Stellar Public Network using TILCAI_NETWORK. Use the SDK/API for Monad; do not assume the MCP already selects it.

Availability depends on your instance. Check /health and /v1/routes before integrating.

TilcAI Docs · 20 Oct 2026Sources and versions ↗