Any MCP client

~alter speaks standard MCP over Streamable HTTP, so any MCP-capable client connects the same way. The generic config below works for any client; stdio-only clients bridge through mcp-remote, and the JSON-RPC endpoint is callable directly with no library. The verified clients below all connect this way. The app clients (Claude, ChatGPT, Le Chat, Perplexity) and developer tools (Claude Code, Codex, Cursor, Cline) each have their own page with tailored steps.

Connection

Setup

{
  "mcpServers": {
    "alter": {
      "url": "https://mcp.truealter.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer <capability_token>" }
    }
  }
}

npx -y mcp-remote https://mcp.truealter.com/api/v1/mcp \
  --header "Authorization:Bearer <capability_token>"

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2025-11-25",
    "capabilities": {},
    "clientInfo": { "name": "my-agent", "version": "1.0.0" }
  }
}

Verify

After initialising, call tools/list to see every tool with its input schema and pricing.

{ "jsonrpc": "2.0", "id": 2, "method": "tools/list", "params": {} }

Notes

• -mcp-remote needs the header as a single key:value token with no space after the colon.
• -Anonymous tools work with no header. The authenticated tools settle per call over x402.

Verified clients

These clients connect to a custom remote MCP server using the generic config above. Each links to its own setup docs.