Skip to main content
The Syntalic MCP server lets AI agents call the Pricing Intelligence API as native tools. The MCP handles wallet setup, multi-chain payment routing, and protocol negotiation automatically — you ask Claude a pricing or social question, the MCP pays and returns the answer.

Install

Requires Node.js 20 or later. The server runs locally over stdio; its source code and changelog are public.
The interactive setup walks through:
  1. Generating a multi-chain wallet (Solana + EVM), or skipping if you want to bring your own keys
  2. Wiring the MCP into Claude Code
Setup adds the server to Claude Code as npx -y @syntalic/mcp-server@latest, so every start runs the newest release. Setup before 0.14.0 left out @latest, and npx can keep running an older cached release. If you set up before then, re-add it:
After setup, fund the wallet with USDC on Solana or Base, or USDC.e on Tempo:
Calls cost $0.01 to $0.05 each, so a few dollars buys hundreds of queries. See Pricing.
Use a dedicated agent wallet, not your primary wallet. The MCP only needs a small balance to operate.

Bring your own keys

To pay from your own keys instead of a generated wallet, set both env vars and run setup:
When setup asks how to set up, type 2 (“Use your own private keys”): it then creates no wallet and only wires the MCP into Claude Code. Pressing Enter, or passing --yes, picks option 1 and generates a wallet anyway. If a wallet file already exists, setup doesn’t ask and prints that wallet’s addresses. Either way the server pays from your keys, so don’t fund the addresses setup prints. When both are set, the wallet file (~/.syntalic/wallet.json) is ignored entirely. Both env vars are required together — setting only one is an error. Make sure your MCP client process also receives both variables; exporting them in one terminal does not persist them to unrelated processes. Never commit keys to your MCP configuration or share exported keys.

Manual MCP config

For Cursor or any other MCP client, or if you skipped the Claude Code step in setup, add this to the client’s MCP configuration:

Choosing the tool set

By default the MCP offers 17 tools: six free discovery tools and eleven paid measure tools, one per measure. To use the per-route tools instead (best_price, price_positioning, ontology_resolve and the rest; 39 tools, the 0.12 set without the unavailable inflation tool), set SYNTALIC_TOOLS=routes:
The value is case-insensitive and whitespace is trimmed; unset or empty selects measures. Any other value stops the server at startup. Use @syntalic/mcp-server@latest to avoid unintentionally running an older cached version. See the changelog for recent changes.

Which chain pays

The MCP tries Solana, then Base, then Tempo. Solana and Tempo are skipped when a balance pre-check shows too little; Base has no pre-check. After a payment attempt, the MCP moves to the next chain on insufficient balance, a network error, or a settlement response it cannot read. Any other rejected payment stops the request, and an API error returned after payment is passed back without trying another chain. Base and Tempo use the same EVM address.
  • In automatic mode an unreadable Solana balance is skipped. If pinned to Solana, the MCP attempts payment even if the balance cannot be read. A dedicated SYNTALIC_SOLANA_RPC_URL can avoid public RPC rate limits.
  • If the Tempo RPC is down, the MCP attempts the payment anyway. Balance checks use short timeouts.
  • To pay on one chain only, set SYNTALIC_PAYMENT_NETWORK to solana, base or tempo.

Configuration

All variables are optional; a wallet is generated on first run. RPC addresses must use HTTPS (localhost is allowed); any other address is ignored and the default is used. SYNTALIC_PAYMENT_NETWORK must be solana, base or tempo; any other value is an error.

CLI commands

What’s next

Available tools

The 17 default tools — six free, eleven measures — with example prompts.

Direct HTTP

Skip the MCP and call the API directly with x402.