Quantish Mcp Setup

Quantish MCP Setup

Sets up 4 MCP servers for prediction market trading:

• Discovery - Search markets across Polymarket, Kalshi, Limitless
• Polymarket - Trade on Polymarket (crypto)
• Kalshi - Trade on Kalshi (CFTC-regulated via Solana)
• Limitless - Trade on Limitless (Base chain)

Instructions

Step 1: Get User's Email

Ask for their email address. Each user needs their own email — it creates a unique account with its own API keys and wallet.

question: "What email should I use for your Quantish account? (Required — each user gets their own keys and wallet)"

Step 2: Get API Keys

Run these 5 curl commands, replacing USER_EMAIL with the email from Step 1:

Polymarket key:

curl -s -X POST https://quantish-sdk-production.up.railway.app/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"request_api_key","arguments":{"externalId":"USER_EMAIL"}},"id":1}'

Extract apiKey from result.content[0].text JSON. Format: pk_live_...

Setup Polymarket trading wallet (REQUIRED — use the key you just got):

The Polymarket API key comes with an EOA address, but that is NOT the trading wallet. You MUST call setup_wallet to create the Safe wallet that is actually used to trade on Polymarket. Without this call, the user cannot place orders.

curl -s -X POST https://quantish-sdk-production.up.railway.app/mcp \
  -H "Content-Type: application/json" \
  -H "x-api-key: POLYMARKET_KEY" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"setup_wallet","arguments":{}},"id":1}'

Extract the safeAddress from the response — this is the wallet the user should send USDC to for trading.

Kalshi key:

curl -s -X POST https://kalshi-mcp-production-7c2c.up.railway.app/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"kalshi_signup","arguments":{"externalId":"USER_EMAIL"}},"id":1}'

Extract apiKey from result.content[0].text JSON.

Limitless key:

curl -s -X POST https://limitless-mcp-server-production.up.railway.app/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"limitless_signup","arguments":{"externalId":"USER_EMAIL"}},"id":1}'

Extract apiKey from result.content[0].text JSON. Format: pk_limitless_... Limitless creates the wallet automatically — the walletAddress in the response is the Base wallet for trading. No separate setup_wallet call needed.

Discovery key:

curl -s -X POST https://quantish.live/api/mcp/discovery-key \
  -H "Content-Type: application/json" \
  -d '{"name":"Claude Code - USER_EMAIL"}'

Extract key from response. Format: qm_...

Step 3: Add All 4 MCP Servers to Claude Code (CRITICAL)

Getting API keys is NOT enough. You MUST run these commands to register each server in your Claude Code configuration. Without this step, none of the MCP tools will be available. Each command should print "Added HTTP MCP server ... to local config" on success.

claude mcp add --transport http quantish-discovery https://quantish.live/mcp --header "X-API-Key: DISCOVERY_KEY"

claude mcp add --transport http quantish-polymarket https://quantish-sdk-production.up.railway.app/mcp --header "x-api-key: POLYMARKET_KEY"

claude mcp add --transport http quantish-kalshi https://kalshi-mcp-production-7c2c.up.railway.app/mcp --header "x-api-key: KALSHI_KEY"

claude mcp add --transport http quantish-limitless https://limitless-mcp-server-production.up.railway.app/mcp --header "x-api-key: LIMITLESS_KEY"

Verify each command printed "Added HTTP MCP server" with exit code 0. If it says "already exists", that server is already configured — that's fine.

Step 4: Tell User to Restart Claude Code (REQUIRED)

MCP servers do NOT become available until Claude Code is restarted. The tools will not appear in the current session. Tell the user:

All 4 MCP servers are configured! You must exit and restart Claude Code for the tools to load.

After restarting, try:
- "Search for Bitcoin markets"
- "Show my Polymarket balance"
- "Show my Kalshi positions"
- "Show my Limitless positions"

Do not skip this step. If the user asks why tools aren't showing up, the answer is always: restart Claude Code.

Notes

• If server already exists, claude mcp add returns exit code 1 with "already exists" - that's fine, it's already configured
• Keys are single-use - same email will NOT return the key again (save it on first signup)
• Discovery has 5 keys/hour rate limit
• All 4 servers must be added via claude mcp add — the API keys alone are useless without this configuration step

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: joinQuantish
• Source: joinQuantish/skills
• License: MIT

Install and usage instructions live in the source repository linked above.