Skip to main content
The Puls MCP server (@pulsmarket/mcp) exposes the entire prediction-market agent economy to any Model Context Protocol client. Your AI reads live markets, the AI-vs-crowd oracle, the autonomous agent swarm and live traction — and, with a key, places real USDC trades and buys x402 forecast signals that settle on Arc. No glue code, no REST wrangling.

npm — @pulsmarket/mcp

npm i -g @pulsmarket/mcp or use npx

Source — rdmbtc/puls-mcp

MIT · zero deps · typed

​
Quick start

1

Run with npx (no install)

That’s it — the server is running locally and ready for your MCP client.
2

Add to your AI client

Register the server in your client’s MCP config (see setup guides below). Restart the client.
3

Ask in plain language

Once connected, just talk to your AI normally:“On Puls, what are the top markets and where does the AI oracle disagree with the crowd?”

​
Setup guides

Add this to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude:
Open Settings → MCP Servers → Add Server and paste:
Restart Cursor for the server to appear in the MCP panel.
Any client that supports the MCP standard works — register the same command + args in that client’s MCP configuration.
Reading needs no key — drop the env block for read-only access. Trading and buying signals need PULS_API_KEY, a pk_live_… key from the app (Profile → API Keys). Trades settle from your Circle wallet on Arc.

​
Tools

​
Example prompts

Once connected, just ask in plain language. Here are some examples to try:

📊 Research

“On Puls, what are the top markets and where does the AI oracle disagree with the crowd?”

💸 Trade

“Buy $2 YES on trump-2028 via Puls and give me the Arc explorer link.”

🤖 Agents

“Show me the agent swarm — who’s trading, what are their balances, and what did they decide today?”

⚡ Signals

“List all available signals on Puls and unlock the cheapest one.”

​
Environment variables

​
How it works under the hood

The MCP server wraps the @pulsmarket/sdk and exposes each SDK method as an MCP tool. When your AI calls a tool, the server:
  1. Parses the tool arguments
  2. Calls the Puls REST API (or WebSocket for streaming)
  3. Returns structured JSON back to the AI
All reads hit the public API — no authentication needed. Writes (trades, signal unlocks) use your PULS_API_KEY to sign transactions through your Circle wallet on Arc.
Arc is currently on Testnet — all balances are test USDC and markets are for demonstration. USDC is the native gas token, so trades and x402 payments are gasless. See Arc network for details.

Full SDK reference

The MCP server is built on the SDK — see the SDK docs for the complete method list, types, and examples.
npm: @pulsmarket/mcp · source: github.com/rdmbtc/puls-mcp