Connect artist.tools to an MCP client

MCP (Model Context Protocol) tool access lets you run artist.tools research and workspace tools from compatible AI clients like ChatGPT, Claude, Cursor, and Grok. It's included in the Developer Access plan and connects over Streamable HTTP with OAuth, so no API key is required.

What MCP tool access does

Connecting an MCP client gives that client access to artist.tools data through a set of tools grouped into Research, Workspace, and Admin. Research tools search and inspect artists, tracks, playlists, curators, keywords, Google rankings, press mentions, Spotify playlist rankings, entity activity, and artist discographies. Workspace tools manage your saved folders, saved keywords, and entity notes. Admin tools support administrator operations and are available only to administrators who approve them.

Connect an MCP client

You connect from the Integrations page or the Developer Console. The client can connect on any plan, but only Developer Access lets it run research and workspace tools.

  1. Open Settings > Integrations and click Connect a client (or Connect another if you already have a connection).

  2. In the Connect an MCP client dialog, copy the server URL from the read-only field.

  3. 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.

  4. Your client opens artist.tools in the browser. Sign in to your account.

  5. 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.

  6. 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

The connection flow recognizes Claude, ChatGPT, Cursor, Grok, Gemini, Perplexity, GitHub Copilot, Windsurf, and Zed, and also accepts unknown clients.

Use cases

  • Research and vetting. Ask a client to search artists, tracks, playlists, or curators, or to pull entity details, track credits, keyword data, Google rankings, press mentions, or playlist Spotify rankings.

  • Workspace management. Use a client to organize your saved folders, saved keywords, and entity notes without leaving your AI tool.

  • Administrator support. Run support operations such as refreshing entities or reviewing playlist quality reports from a connected client.

Requirements and access

Normal research and workspace tools require Developer Access. The who_am_i tool is available on all plans. Users on other plans can connect but see "On your current plan this client can connect but can't run tools yet." Administrator tools are available only to current administrators whose connection explicitly approved administrator access.

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 the full tool inventory and rate limits, see MCP tools, access, and rate limits. For the OAuth endpoints and token lifetimes, see MCP authentication and OAuth.

Was this helpful?