MCP Integration Guide
Start a workspace-bounded stdio KabuForge MCP server and understand default access and local paper opt-in.
Choose your client
Start with a bounded workspace
kabuforge mcp --workspace output/agent_workspaceConfigure your MCP client to launch the installed kabuforge command with these arguments. The server implements JSON-RPC 2.0 initialization, ping, tools and resources over stdio.
Inspect before calling
Use get_capabilities, factor and strategy catalogs, run inspection and kabuforge:// resources. Each call validates its exact schema and records a durable receipt. Paths stay inside the workspace; protected directories, secrets and the audit database are excluded.
Access tiers
| Tier | Boundary |
|---|---|
| R0 | Read-only inspection; enabled by default. |
| R1 | Local validation, analysis, planning, demo, backtest, comparison and cancellation; default access. |
| R2 | Workspace drafts and local paper simulation; explicit opt-in required. |
| R3 | Reserved external interfaces; disabled. |
Enable local paper only when needed
kabuforge mcp --workspace output/agent_workspace --enable-paperR2 calls require agent_call_id and idempotency_key. Do not retry an uncertain mutation under a new identity. This switch grants local simulation access only.
Applies to: v0.1.1 · Public source docs/en_US/AGENT_API.md
Reviewed · KabuForge