SongPilot MCP Server
Official# songpilot-mcp (archived)
This adapter is retired. SongPilot now runs a hosted MCP server, so there is
nothing to install.
To connect Claude, add a custom connector with this URL and sign in to
SongPilot:
```
https://app.songpilot.ai/agents/mcp
```
Claude Code:
```bash
claude mcp add --transport http songpilot https://app.songpilot.ai/agents/mcp
```
Setup: https://songpilot.ai/mcp
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of an agent confusing it with another tool. Its purpose (routing natural-language requests to SongPilot specialists) is unambiguous by construction.
The lone name 'run_orchestrator' follows a clear verb_noun snake_case pattern. With a single tool, consistency is trivially satisfied and the name is readable and descriptive.
A single catch-all tool is very thin for the apparent breadth of the domain (artwork, release planning, bios, song status, artist profiles). The router pattern is deliberate, but agents get no discoverable capability surface beyond one opaque entry point.
There are no structured operations for core entities like songs, albums, artists, or releases — no list/get/create/update equivalents. Everything must go through free-text routing, so agents cannot perform predictable, verifiable actions and will fail on tasks requiring structured access.