Using MCP
MCP (Model Context Protocol) lets an IDE or desktop host (Cursor, Claude Code, Claude Desktop, Grok Build) call Artifice jester_* tools — the same execution plane as Console chat and the Jester Mini App Agent — without opening the terminal.
You need this if you want your coding assistant to read portfolio and strategy context, or to run governed actions from your editor.
Setup: MCP setup
HTTP wallet bots (no MCP): API access
What MCP gives you
| Capability | Description |
|---|---|
| Tool-only | Your host model reasons. Artifice supplies data and executes confirmed actions via jester_* tools. |
| Full-chat | Call jester_agent_chat so the server-side harness answers (prefetch, tiers, mesh) — same as Console / Mini App Agent. |
| Governed writes | Destructive actions require confirmation. |
| Scoped reads | Portfolio, positions, strategies, backtests, automation health — within your account |
Start with tool-only. Your IDE model does the reasoning. You do not need a separate provider key on Artifice for that mode.
Choose your integration
| You are building… | Use |
|---|---|
| Cursor / Claude / Grok / local IDE assistant | MCP (this guide + setup) |
| OpenClaw, Hermes, custom wallet bot | HTTP (API access) |
| Chat in Console | Agent (overview) |
| Chat in Telegram or Mini App | jester.trade Agent |
Prerequisites
- An Artifice account. Sign in at Console.
- An API key from Console Keys or agent onboarding.
- Node.js 18+ so the host can run
npx -y jester-mcp-bridge. - Full-chat only: a provider key saved on the trading account if you use
jester_agent_chat.
Quick start
- Issue a key in Console. Store it securely.
- Add the MCP server in your host. See MCP setup.
- Restart the host.
- Ask it to list Jester tools. You should see
jester_*names.
List my open positions and unrealized PnL using Jester tools.
What are the top backtested strategies this week? Do not subscribe yet.
Summarize my automation health and any strategies that failed parity checks.
For full-chat (server-side harness):
Use jester_agent_chat: recommend what I should subscribe to using blended live and backtest ranking.
Tool-only vs full-chat
| Mode | Who writes the answer | Provider key on Artifice |
|---|---|---|
| Tool-only | Your MCP host (Cursor, Claude, etc.) | Not required |
| Full-chat | Server-side harness via jester_agent_chat | Required on the trading account |
Start with tool-only if you already pay for a model in your IDE. Use full-chat when you want identical behavior to Console chat / the Mini App Agent tab.
Safety
- Treat API keys like trading credentials.
- Review confirmation prompts before approving trades or automation changes.
- Prefer read-only calls first.
- Revoke keys when you disconnect a host.
See Safety.
Troubleshooting
| Symptom | Check |
|---|---|
No jester_* tools | Host restarted; Node 18+; API key and base URL set; npx -y jester-mcp-bridge reachable |
| Auth errors | Key copied correctly and has not been revoked |
| Full-chat fails | Provider key is saved on the trading account |
| Action blocked | Confirmation required — re-run after reviewing the summary |