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