npx.
Configure your client
The server runs over stdio and readsPARLAYX_KEY_ID and
PARLAYX_PRIVATE_KEY_HEX from the client’s env block. Nothing is passed as a
tool argument.
- Claude Code
- Codex
- Other clients
-- before the command is required, and at least one other option has to
sit between the last --env and the server name, or the CLI reads the name as
another env pair.Add --scope project to write it into the project’s .mcp.json rather than
your user configuration.npx -y @parlayx/mcp, and the published
binary is parlayx-mcp if you would rather install the package and run it
directly.
Check that it connected
The server validates your key before it opens the transport, so a bad credential fails at startup rather than on the first tool call. A healthy start writes one line to stderr:claude mcp list reports the server’s health directly. In any
client, listing the available tools is the quickest check: you should see
seventeen parlayx tools, all of them reads.
If the server is missing, or no tools appear, see
Troubleshooting.
Your first call
Ask your agent something that only your key can answer:Which ParlayX pod does my key act for, and what can it do?That runs
whoami. A reply naming your actor and pod confirms the credentials
are right and the signature was accepted.
From there:
List the sports on ParlayX, then find today’s baseball events and show me the markets on the first one.
What are my Polymarket and Kalshi balances, and do I have any open positions?
Discovery listings report
venue in upper case (POLYMARKET, KALSHI), while the tools are
named polymarket_* and kalshi_*. Read the venue off the listing and pick the matching tool.Trading stays off until you ask for it
Everything above is read-only, and that is all the server offers until you deliberately turn trading on. See Tools for what that takes and what it exposes.Tools
Every tool, what it returns, and how the trading opt-in works.