Synapse MCP Server

Official SynapseNetwork MCP server for agent payments, service discovery, and receipts.

Remote serverstreamable-httpPython

What is the Synapse MCP server?

Connect Synapse to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Official SynapseNetwork MCP server for agent payments, service discovery, and receipts. The synapse mcp server is what makes that connection.

What the server does

Synapse Network MCP Server for paid API calls is the official Model Context Protocol (MCP) server from SynapseNetworkAI. "Synapse Network MCP" with a space and "SynapseNetwork MCP" without a space refer to this same SynapseNetworkAI/Synapse-Network-MCP-Server project. It gives ChatGPT custom MCP apps, Claude connectors, Cursor, Claude Desktop, Devin, and MCP-compatible agent frameworks a stateless way to discover external APIs, invoke them, and retrieve receipts through SynapseNetwork agent payments.

  • No in-memory discovery cache
  • No local persistence
  • No Synapse SDK import
  • No owner, admin, or provider control-plane tools
  • Direct Gateway HTTP calls with native fetch
  • Money values stay decimal strings at every boundary

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • discover_services — Outputs include agent-facing service metadata, schemas, health, and pricing fields such as priceUsdc for fixed-price APIs or token-metered pricing
  • invoke_and_pay — For fixed-price APIs, costUsdc must match the discovered price. If the price is stale or copied incorrectly, Gateway returns PRICE_MISMATCH
  • get_receipt — Gateway enforces that the receipt belongs to the configured Agent Key

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: SYNAPSE_AGENT_KEY, SYNAPSE_ENV, SYNAPSE_GATEWAY_URL, SYNAPSE_TIMEOUT_MS, SYNAPSE_E2E_AGENT_KEY_SOURCE, SYNAPSE_E2E_SERVICE_ID, SYNAPSE_E2E_PAYLOAD_JSON, SYNAPSE_E2E_COST_USDC. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Synapse's toolset — discover_services, invoke_and_pay, get_receipt — is a fair guide to whether it matches your workflow. It is maintained by SynapseNetworkAI; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
discover_servicesOutputs include agent-facing service metadata, schemas, health, and pricing fields such as priceUsdc for fixed-price APIs or token-metered pricing fields for LLM services. Provider payout, ledger, internal routing, and s
invoke_and_payFor fixed-price APIs, costUsdc must match the discovered price. If the price is stale or copied incorrectly, Gateway returns PRICE_MISMATCH; rediscover and retry only if the user or task permits the current price.
get_receiptGateway enforces that the receipt belongs to the configured Agent Key.

How to install the Synapse MCP server

{
  "mcpServers": {
    "synapse-network": {
      "command": "npx",
      "args": ["-y", "@synapse-network-ai/mcp-server"],
      "env": {
        "SYNAPSE_AGENT_KEY": "your-value",
        "SYNAPSE_ENV": "your-value",
        "SYNAPSE_GATEWAY_URL": "your-value",
        "SYNAPSE_TIMEOUT_MS": "your-value",
        "SYNAPSE_E2E_AGENT_KEY_SOURCE": "your-value",
        "SYNAPSE_E2E_SERVICE_ID": "your-value",
        "SYNAPSE_E2E_PAYLOAD_JSON": "your-value",
        "SYNAPSE_E2E_COST_USDC": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SYNAPSE_AGENT_KEYCredential the server authenticates with.Yes
SYNAPSE_ENVConfiguration value read at startup.Optional
SYNAPSE_GATEWAY_URLEndpoint or connection string the server talks to.Yes
SYNAPSE_TIMEOUT_MSConfiguration value read at startup.Optional
SYNAPSE_E2E_AGENT_KEY_SOURCECredential the server authenticates with.Yes
SYNAPSE_E2E_SERVICE_IDConfiguration value read at startup.Optional
SYNAPSE_E2E_PAYLOAD_JSONConfiguration value read at startup.Optional
SYNAPSE_E2E_COST_USDCConfiguration value read at startup.Optional

Example prompts to try

  • Use Synapse to discover services.
  • Use Synapse to invoke and pay.
  • Use Synapse to get receipt.

Frequently asked questions

It connects Synapse to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (discover_services, invoke_and_pay, get_receipt) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Synapse directly.