Skip to main content
@parlayx/mcp is the official Model Context Protocol server for the ParlayX API. Your MCP client runs it on your own machine and your agent can then answer questions like:
  • “What is my Polymarket balance, and which positions am I holding?”
  • “Which baseball games have markets today, and on which venues?”
  • “Did my last order fill, and at what price?”
  • “This Kalshi ticker: what event is it, and does Polymarket quote the same outcome?”
Seventeen read tools cover identity, sports discovery, orders, fills, positions and balances. Four trading tools place and cancel orders, and register only when you turn them on. The full list is in the Tools reference. Reach for the MCP server when a person is in the loop. Write against the SDK when a program is. Both call the same public API, and a key does through one exactly what it does through the other.

​
Security

Your ParlayX private key is a signing key for real money. Treat the MCP client’s configuration file as a secret file, and prefer a client that can read the seed from your shell environment rather than storing it inline.
  • Your key stays on the machine. The server signs each request in its own process. Only the key id, a timestamp and the signature go on the wire.
  • Trading is off by default. The four order tools register only when you set PARLAYX_MCP_ALLOW_TRADING=1 and the key carries the trade capability. Without both, they are not advertised, so nothing can reach them.

​
Requirements

Node.js 20 or newer, and a ParlayX key id with its Ed25519 private key seed. See Authentication for how keys are issued and revoked. Signing needs the key in the running process, so the server belongs on a machine you control rather than a browser or an edge runtime. Published on npm under the MIT license.

Quickstart

Configure the server for Claude Code, Claude Desktop or Cursor, and make your first call.