mission_status — Field Ops MCP Tool
mission_status
(mission status) is one of 4 tools on the
Field Ops
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mission_status from your client
- Claude Code Field Ops mission_status run in your project directory
- Claude Desktop Field Ops mission_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Field Ops mission_status ~/.cursor/mcp.json
- VS Code Field Ops mission_status .vscode/mcp.json
- Zed Field Ops mission_status ~/.config/zed/settings.json
- Windsurf Field Ops mission_status ~/.codeium/windsurf/mcp_config.json
- Cline Field Ops mission_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Field Ops mission_status ~/.gemini/settings.json
- Grok Field Ops mission_status .mcp.json (in your project root)
- ChatGPT Field Ops mission_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Field Ops mission_status Settings → Connectors → Add custom connector
- LangChain Field Ops mission_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http field-ops https://field-ops.filnith.workers.dev/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.