KabuForge
Menu
GitHub日本語

Generic stdio MCP

Connect stdio to the local KabuForge MCP server using existing configuration examples, absolute paths and verification steps.

Environment and paths

In a Python 3.12+ source checkout, run python -m pip install -e . and check kabuforge doctor. Replace both the executable and dedicated workspace with absolute paths. On Windows use command C:/path/to/venv/Scripts/kabuforge.exe and workspace C:/path/to/agent_workspace. Keep secrets out of JSON.

Configuration excerpt

The client sends newline-delimited JSON-RPC to stdin and reads responses from stdout.

/absolute/path/to/venv/bin/kabuforge --locale en_US mcp --workspace /absolute/path/to/agent_workspace

Verify the connection

Send these UTF-8 JSON requests one line at a time through the client’s stdin connection. stdout is reserved for the protocol; inspect stderr for logs. Notifications have no response.

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"local-check","version":"1.0"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":2,"method":"tools/list"}

Verify and continue

Verify initialize → notifications/initialized → tools/list. Research inputs are explicit workspace files. Paper writes are disabled by default; broker order submission is unsupported. Existing MCP examples · Agent API contract

Official client / transport documentation

Applies to: main source candidate (unpublished) · Public source examples/mcp/README.md

Reviewed · KabuForge