musicatlas-track-results — musicatlas MCP Resource

musicatlas-track-results is one of 1 resource on the musicatlas MCP server. Connect the server and your client can attach it as context.

by client

How to attach musicatlas-track-results from your client

• Claude Code musicatlas Resource/musicatlas-track-results run in your project directory
• Claude Desktop musicatlas Resource/musicatlas-track-results ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor musicatlas Resource/musicatlas-track-results ~/.cursor/mcp.json
• VS Code musicatlas Resource/musicatlas-track-results .vscode/mcp.json
• Zed musicatlas Resource/musicatlas-track-results ~/.config/zed/settings.json
• Windsurf musicatlas Resource/musicatlas-track-results ~/.codeium/windsurf/mcp_config.json
• Cline musicatlas Resource/musicatlas-track-results ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI musicatlas Resource/musicatlas-track-results ~/.gemini/settings.json
• Grok musicatlas Resource/musicatlas-track-results .mcp.json (in your project root)
• ChatGPT musicatlas Resource/musicatlas-track-results Settings → Connectors → Advanced → Developer mode
• Claude.ai musicatlas Resource/musicatlas-track-results Settings → Connectors → Add custom connector
• LangChain musicatlas Resource/musicatlas-track-results pip install langchain-mcp-adapters

Read from the server itself, by connecting to it and calling resources/list on 28 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.