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