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