Skip to main content
Some MCP clients can’t attach custom headers to remote HTTP servers (for example Claude Desktop’s config-file setup). Bridge them with mcp-remote, which runs locally as a stdio server and forwards to SeeSaw with your key: 
{
  "mcpServers": {
    "seesaw": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.seesaw.fun/mcp",
        "--header",
        "Authorization: Bearer sspat_YOUR_KEY"
      ]
    }
  }
}
For Claude Desktop, this goes in claude_desktop_config.json (Settings → Developer → Edit Config), then restart the app. Requires Node.js ≥ 18 on the machine running the client.

​
Verify

After a restart, the client’s tools list should show 14 SeeSaw tools. Ask:
What prediction markets are ending soon on SeeSaw?

​
Troubleshooting

SymptomLikely cause
Server never appearsnpx not on PATH (install Node.js), or JSON syntax error
Auth errors in logsKey typo in the --header argument
Works then stopsKey revoked, or rate limited — see Rate limits

​
Any MCP SDK

The endpoint is standard Streamable HTTP, so every MCP SDK connects directly — pass the Authorization header in your transport config, e.g. in TypeScript: 
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const transport = new StreamableHTTPClientTransport(
  new URL("https://api.seesaw.fun/mcp"),
  { requestInit: { headers: { Authorization: "Bearer sspat_YOUR_KEY" } } }
);
const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);