get_canon_history — Continuity MCP Tool Read-only
get_canon_history
(get canon history) is one of 11 tools on the
Continuity
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_canon_history from your client
- Claude Code Continuity get_canon_history run in your project directory
- Claude Desktop Continuity get_canon_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Continuity get_canon_history ~/.cursor/mcp.json
- VS Code Continuity get_canon_history .vscode/mcp.json
- Zed Continuity get_canon_history ~/.config/zed/settings.json
- Windsurf Continuity get_canon_history ~/.codeium/windsurf/mcp_config.json
- Cline Continuity get_canon_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Continuity get_canon_history ~/.gemini/settings.json
- Grok Continuity get_canon_history .mcp.json (in your project root)
- ChatGPT Continuity get_canon_history Settings → Connectors → Advanced → Developer mode
- Claude.ai Continuity get_canon_history Settings → Connectors → Add custom connector
- LangChain Continuity get_canon_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http continuity https://continuitywriter.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.