Connect artist.tools to an MCP client
Connect any compatible AI client to your artist.tools account through a hosted remote MCP server. Every plan can connect, and the client can run the tools your plan allows: 10 on Free, 17 on Artist, and all 34 ordinary tools on Industry and Developer.
What the connection gives your client
The connection gives an AI agent access to your artist.tools research and workspace tools: searching artists, tracks, playlists, and curators, pulling entity details, track credits, keyword data, Press Mentions, and organizing results into your folders, saved entities, saved keywords, and notes. It is a hosted music-intelligence server, not a Spotify playback remote: it cannot play, queue, or change music on your Spotify account or your personal Spotify library.
Your plan and permissions are checked on every tool call. If you change plans, the change takes effect on the client's next call without reconnecting. A call your plan does not cover returns a clear plan_required error naming the required plan, and the OAuth connection stays active.
Connect an MCP client
You set up the connection from Settings > Integrations. You only need your artist.tools account; no Developer API key and no Spotify credentials are involved.
Open Settings > Integrations and click Connect a client (or Connect another if you already have a connection).
In the Connect an MCP client dialog, copy the server URL from the read-only field.
In your AI client, add artist.tools as a remote MCP server using that URL. Most clients call this a connector, remote server, or HTTP MCP server.
Your client opens artist.tools in the browser. Sign in to your account.
Review the consent screen, which shows the client, the account you're authorizing as, the redirect URI, and the access the connection requests. Choose Authorize, or Deny to cancel, or Switch account to sign in as someone else.
Ask the client to look up an artist to confirm the tools are reachable.
The dialog footer notes the transport and auth: Auth: OAuth 2.1 · Transport: streamable HTTP. A Setup docs link opens the full developer documentation.
Supported clients
ChatGPT, Claude, Cursor, and Grok are examples of clients that can connect; they are not an allowlist. Any client that supports remote MCP servers over Streamable HTTP and can complete the OAuth flow can connect, and every client receives the same protocol-level connection and account-level permissions.
Requirements and access
Your client discovers all 34 ordinary tools on any plan, but only the tools your plan covers execute.
Plan | Tools the client can run |
|---|---|
Free | 10 tools: account context, documentation search, saved dashboard entities, entity folders, and notes, including changes to existing folders. |
Artist | 17 tools: adds folder creation, entity resolution and detail, playlist search, track credits, artist discography, and playlist Discovered On. |
Industry | All 34 ordinary tools: adds the remaining search, keyword, rankings, Press Mentions, and entity Activity tools. |
Developer | The same 34 ordinary tools as Industry, with higher MCP rate limits. |
For the complete tool list by plan and the rate limits, see MCP tools, access, and rate limits.
Separate administrator tools sit outside the ordinary tool catalog and are not part of any plan's tool set. They are available only to current administrators who explicitly approved administrator access on the connection.
Manage connected clients
Connected clients appear under Settings > Integrations in the MCP clients card. Open Details to see the client's website, when it was authorized, its last use, its scopes, administrator access (Approved or Not approved), and its client ID. Disconnect removes that client's access immediately.
Next steps
For registration, endpoints, and token lifetimes, see MCP authentication and OAuth. You can disconnect a client or review its recent activity at any time from Settings > Integrations.