Connecting AI Clients
2026-11-15
With the MCP service on, register the app in your AI client's config and Codex, Claude, Qoder, WorkBuddy and friends can create chapters, edit body text and operate mind maps and canvases directly. Enabling the service and tool permissions: MCP & External AI. This page is the per-client setup.
How it works
Every client launches the app's bundled bridge the same way: command = the app's install path, args = --mcp-stdio. While the app runs, the bridge forwards requests to it; without the app, tools are unavailable. Any client that supports "stdio MCP servers" can connect this way.
Don't hand-type the path: "Settings → MCP services → Manual configuration" generates ready-to-paste snippets pointing at your local install.
Claude Code
Automatic: open "Settings → MCP services" and click "Detect" — on the Claude Code row click "One-click write"; it registers into ~/.claude.json with a backup first.
Manual (pick one):
- Command line:
claude mcp add biglazycat -- "<install path>" --mcp-stdio; - Edit
~/.claude.json, merging intomcpServers:
{
"mcpServers": {
"biglazycat": {
"command": "<install path>",
"args": ["--mcp-stdio"]
}
}
}
- For a single project: put the same entry into
.mcp.jsonin the project root.
Restart Claude Code for the config to take effect.
Claude Desktop
Claude Desktop reads the same mcpServers shape from claude_desktop_config.json (Windows: %APPDATA%\Claude\, macOS: ~/Library/Application Support/Claude/). Merge the biglazycat entry, restart, and the tools appear in the conversation's tool menu.
Codex CLI
Automatic: after "Detect", click "One-click write" on the Codex CLI row; it registers into ~/.codex/config.toml.
Manual: add to ~/.codex/config.toml:
[mcp_servers.biglazycat]
command = '<install path>'
args = ["--mcp-stdio"]
Single-quoted TOML literals keep Windows backslashes as is. Restart Codex CLI.
Qoder
- Open settings in Qoder (
Ctrl+Shift+,, macOS⌘⇧,) and choose "MCP" in the sidebar; - Click "+ Add" at the top right of "My services", transport STDIO;
- Name
biglazycat, command = the app's install path (copy from "Manual configuration"), args--mcp-stdio, save; - Or from the command line:
qoder mcp add biglazycat -- "<install path>" --mcp-stdio.
Available in Qoder sessions right after saving.
WorkBuddy
- Open "Settings → Connectors → Add service", transport stdio, command = the app's install path, args
--mcp-stdio; - Or edit
~/.workbuddy/mcp.jsondirectly (Windows:.workbuddy\mcp.jsonin your user folder), merging the samemcpServersentry as Claude; - WorkBuddy requires manual trust for new servers: find biglazycat under connector management and click "Trust".
OpenCode and Gemini CLI
Both are on the "Detect" list — one click registers them. Manual snippets are under "Manual configuration" too: OpenCode uses a local server under the mcp key (command as an array), Gemini CLI uses mcpServers in ~/.gemini/settings.json. Restart after configuring.
Once connected
- Have the AI call
get_app_guidefirst to learn your workspace before touching anything; - Untick tools you don't want to expose under "Settings → MCP services" — effective immediately;
- Body-text writes go through the app's confirmation flow; changes roll back via Version History;
- Every call is logged under "Settings → AI call logs".
Not working?
- The app must be running: quitting from the system tray stops the service — closing the window alone does not;
- Written configs take effect after restarting that client;
- Installed a new client? Click "Re-detect";
- If a config file with comments blocks the automatic write, merge manually as prompted;
- "A same-name config exists but was not written by this app" means a conflicting entry — check it manually before merging.