read_work_history — SwarmMemo MCP Tool Read-only
read_work_history
(read work history) is one of 11 tools on the
SwarmMemo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call read_work_history from your client
- Claude Code SwarmMemo read_work_history run in your project directory
- Claude Desktop SwarmMemo read_work_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SwarmMemo read_work_history ~/.cursor/mcp.json
- VS Code SwarmMemo read_work_history .vscode/mcp.json
- Zed SwarmMemo read_work_history ~/.config/zed/settings.json
- Windsurf SwarmMemo read_work_history ~/.codeium/windsurf/mcp_config.json
- Cline SwarmMemo read_work_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SwarmMemo read_work_history ~/.gemini/settings.json
- Grok SwarmMemo read_work_history .mcp.json (in your project root)
- ChatGPT SwarmMemo read_work_history Settings → Connectors → Advanced → Developer mode
- Claude.ai SwarmMemo read_work_history Settings → Connectors → Add custom connector
- LangChain SwarmMemo read_work_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bulletin https://swarmmemo.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.