@thedeck/mcp
v0.1.5
Published
The Deck's MCP server. It lets your AI agent draft tasks, send blanked example copies, propose tests, check your tasks and their passing entries, run the pre-check on your entry, and try passing entries on your real data. It acts as you, with the same rig
Readme
@thedeck/mcp
The Deck's MCP server. It lets your AI agent draft tasks, send blanked example copies, propose tests, check your tasks and their passing entries, run the pre-check on your entry, and try passing entries on your real data. It acts as you, with the same rights you have on the site.
An agent can never save a card, post a task live, accept an entry, pitch in or pay anyone. You do those on The Deck yourself.
Connect
Claude Code:
claude mcp add thedeck -- npx @thedeck/mcpCodex:
codex mcp add thedeck -- npx @thedeck/mcpGitHub Copilot in VS Code:
code --add-mcp '{"name":"thedeck","command":"npx","args":["@thedeck/mcp"]}'The first time your agent uses a tool, your browser opens The Deck's consent page. Sign in, check what the
agent may do, and press Allow. The sign-in is saved in ~/.thedeck/credentials.json; disconnect the agent
any time in Settings › Agent.
ChatGPT and other clients that only connect to remote servers use https://thedeck.dev/mcp instead. That
address has the poster tools and deck.report_issue only: nothing there runs on your computer. In Grok, open
Connectors, choose New Connector, then Custom, enter that address and sign in to The Deck when asked.
Tools
| Tool | For | Runs |
|---|---|---|
| deck.post_draft | posters | The Deck |
| deck.add_example_copy | posters | checks the copy here, then The Deck; over /mcp, after you approve the exact copy in the chat |
| deck.propose_tests | posters | The Deck, after you approve the test plan in the chat |
| deck.list_quests | posters and builders | The Deck |
| deck.get_task_status | posters | The Deck |
| deck.get_passing_entries | posters | The Deck |
| deck.try_on_real_data | posters | a sandbox on this computer |
| deck.run_precheck | builders | a sandbox on this computer |
| deck.report_issue | posters and builders, during the beta, with your yes | The Deck |
Real files and real data never leave your computer: only blanked copies and scores do.
The local sandbox
deck.run_precheck and deck.try_on_real_data run entries the way The Deck's runner does, in a Docker
container with no network. Install Docker and build the sandbox image once from this repository:
docker build -f runner/Dockerfile --target sandbox -t thedeck-sandbox .An entry folder needs a deck.json naming the command that runs it, for example
{"run": ["python", "read_invoices.py", "{input}", "{output}"]}. Without {output}, what the program
prints is its answer.
For deck.try_on_real_data, put each real input beside its right answer with the same name, such as
invoice-01.pdf and invoice-01.csv.
Pre-check from a terminal
npx -p @thedeck/mcp thedeck precheck <quest id> [entry folder]Settings
THEDECK_URL points the server at another copy of The Deck, for example http://127.0.0.1:3000 locally.
