The loop is deliberately small — find the service, call it, read the receipt — and the server keeps no cache and no local state. Money values stay decimal strings at every boundary, and an unauthenticated call gets a 401 with protected-resource metadata rather than a partial answer.
The official SynapseNetworkAI MCP server for paid API calls. It is a thin adapter over the SynapseNetwork Gateway: it does not hold custody, pricing memory or admin workflows, it just gives an agent the discover-invoke-receipt loop.
- discover_services — read-only discovery of the services available to call
- invoke_and_pay — call a paid API and settle it through the Gateway; a consequential action that should sit behind human approval in your client
- get_receipt — read the receipts recorded against the linked credential
Either the hosted endpoint at https://mcp.synapse-network.ai/mcp for clients that speak Streamable HTTP, or the npm package `@synapse-network-ai/mcp-server` run locally over stdio. Local runs need `SYNAPSE_AGENT_KEY`, a Synapse Agent Key beginning with `agt_`, which the server sends as the Gateway credential header; `SYNAPSE_ENV` picks prod or staging and `SYNAPSE_GATEWAY_URL` overrides the base URL. Hosted clients authenticate with `Authorization: Bearer`. An OpenAI, Anthropic or xAI key is not a Synapse billing credential and must not be forwarded.
One command plus a key — npx -y @synapse-network-ai/mcp-server, then supply credentials