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