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