request_full_report — TrackForge MCP Tool
request_full_report
(request full report) is one of 4 tools on the
TrackForge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call request_full_report from your client
- Claude Code TrackForge request_full_report run in your project directory
- Claude Desktop TrackForge request_full_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TrackForge request_full_report ~/.cursor/mcp.json
- VS Code TrackForge request_full_report .vscode/mcp.json
- Zed TrackForge request_full_report ~/.config/zed/settings.json
- Windsurf TrackForge request_full_report ~/.codeium/windsurf/mcp_config.json
- Cline TrackForge request_full_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TrackForge request_full_report ~/.gemini/settings.json
- Grok TrackForge request_full_report .mcp.json (in your project root)
- ChatGPT TrackForge request_full_report Settings → Connectors → Advanced → Developer mode
- Claude.ai TrackForge request_full_report Settings → Connectors → Add custom connector
- LangChain TrackForge request_full_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http music-registration-check https://api.trackforge.studio/api/v1/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 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.