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