TL;DR

A Spotify MCP Server for Music Intelligence, Not Playback

Most Spotify MCP servers are designed as remote controls. They play songs, change the volume, manage your queue, or modify personal Spotify playlists.

artist.tools MCP solves a different problem.

It gives your AI agent access to the music-industry research and workflow tools available inside artist.tools. You can ask an agent to find playlists that match a campaign, investigate an artist’s growth, resolve a track from an ISRC, compare Spotify keywords, review playlist quality, find curator contact opportunities, inspect backlinks, or organize research into folders.

You do not need to install a local server, create a Spotify Developer application, or give an agent your Spotify credentials. Add the hosted artist.tools MCP endpoint, sign into your artist.tools account, approve the connection, and start working.

What Your AI Agent Can Do in artist.tools

Your connected agent receives a catalog of clearly defined tools rather than unrestricted access to the application.

The exact catalog is visible inside artist.tools and through MCP tool discovery, allowing compatible clients to understand the available inputs, filters, and limits automatically.

Explore the broader artist.tools feature catalog to see the analytics and research capabilities available throughout the platform.

Ask for the Work, Not the Query Parameters

You do not need to memorize tool names or construct API requests. Describe the outcome you want, and your client can choose the appropriate artist.tools tools.

Try requests like:

How the Spotify MCP Connection Works

1. Add artist.tools to your AI client

Open Settings → Integrations in artist.tools and copy your MCP server URL.

Add it to any client that supports remote MCP servers over Streamable HTTP. Your client may call this a connector, custom connector, remote server, or MCP integration.

2. Sign in and approve the connection

Your AI client opens artist.tools in your browser.

Sign into your existing account and review the requested access. You never need to paste your artist.tools password, Spotify password, API key, or OAuth token into the client.

3. Start working with your account

Once approved, the client discovers the available artist.tools tools and can call them on your behalf.

Your plan and permissions are checked on every tool call. You can review connected clients, see recent activity, or revoke a connection at any time from Integrations.

Use the Workspace You Already Built

The MCP connection is not a separate AI workspace.

Your agent works with the same folders, saved keywords, entities, and notes you use on the artist.tools website. Research completed through an AI client remains useful when you return to the application, and work started on the website can be continued through the agent.

This makes longer workflows possible:

1. Search for relevant playlists.

2. Investigate their audience, history, contacts, and quality.

3. Create a campaign folder.

4. Save the strongest candidates.

5. Add notes explaining the selection.

6. Return later and ask the agent to continue from the saved research.

The agent does not need to remember everything from an earlier conversation because the useful context can live in your artist.tools account.

Built for Real Music-Industry Workflows

Artists and Managers

Research playlist placements, audience movement, track performance, potential campaign partners, press coverage, and risk around your catalog. Use Spotify analytics to understand what is growing, then ask your agent to investigate the surrounding playlists, curators, and search visibility.

Labels and Distributors

Compare artists across a roster, investigate unusual growth, review playlist ecosystems, organize release research, and gather context for support or campaign decisions.

Playlist Curators

Use Spotify SEO tools to research keywords, compare competing playlists, identify search opportunities, inspect curator networks, and organize playlist strategy.

A&R and Market Research

Search artists and tracks using growth signals, genres, popularity, streams, release dates, playlist activity, and market context.

Music Marketing and PR

Connect Spotify activity with Google visibility, backlinks, press mentions, keyword movement, and campaign research.

Developers and Operators

Use natural-language agents for interactive investigation while keeping the separate artist.tools Developer API available for deterministic software integrations.

One MCP Server, Any Compatible Client

artist.tools is not limited to a hard-coded list of AI products.

If a client supports remote MCP servers over Streamable HTTP and can complete the standard OAuth flow, it can connect to the same artist.tools endpoint.

That includes clients such as ChatGPT, Claude, Cursor, Grok, and other compatible applications—but those are examples, not an allowlist. Every client receives the same protocol-level connection and account-level permissions.

MCP vs. the artist.tools Developer API

The artist.tools MCP server and Developer API serve different use cases.

Use MCP when you want an agent to work alongside you. Use the Developer API when you are building software that needs predictable programmatic access.

Permissions, Plans, and Control

Any artist.tools account can authorize an MCP connection and confirm its account context.

Running the full research and workspace tool catalog currently requires the Developer Access plan. If your plan changes, the connection can remain authorized, but each tool call is evaluated against your current access.

Some tools only read data. Others can modify your artist.tools workspace by creating or renaming folders, adding or removing saved entities, saving keywords, or updating notes. The authorization screen explains these capabilities before you approve the connection.

You can disconnect a client at any time from Settings → Integrations. Revoking it immediately prevents the client from using its existing access or refresh tokens.

Tool calls are subject to account and per-tool rate limits. If a limit is reached, the agent receives a structured response explaining how long it should wait before trying again.

FAQ

What is a Spotify MCP server?

A Spotify MCP server gives an AI client a standardized set of tools for working with Spotify-related capabilities. Some servers focus on playback and personal libraries. artist.tools MCP focuses on professional music research, Spotify analytics, Spotify SEO, playlist intelligence, curators, backlinks, folders, and notes.

Is this an official Spotify MCP server?

No. artist.tools MCP is an artist.tools product and is not operated or endorsed by Spotify. It works with Spotify-related data and artist.tools capabilities but does not represent an official Spotify MCP product.

Can artist.tools MCP control Spotify playback?

No. It does not play, pause, skip, queue, or change music on your Spotify account. It is designed for research and music-industry workflows rather than personal playback control.

Do I need a Spotify Developer account or API key?

No. artist.tools hosts the MCP server. You connect it to your artist.tools account through OAuth without creating a Spotify Developer application or installing a local server.

Which AI clients can connect?

Any client that supports remote MCP servers over Streamable HTTP and the required OAuth flow can connect. This may include ChatGPT, Claude, Cursor, Grok, and other compatible clients. These examples are not an exclusive list.

What can an AI agent change in my account?

Ordinary MCP tools can manage artist.tools workspace data such as folders, saved entities, saved keywords, and notes. They do not modify Spotify playback, your personal Spotify library, or Spotify-owned artist data.

Is MCP the same as the artist.tools Developer API?

No. MCP is an account-aware tool interface for AI agents. The Developer API is a separate programmatic interface into artist-tools-data for software integrations.

What artist.tools plan includes MCP?

Any account can authorize a connection and confirm its account context. Running the complete research and workspace tool catalog currently requires Developer Access.

Can I revoke an MCP connection?

Yes. Connected clients are listed under Settings → Integrations. Revoking a connection immediately invalidates its access and refresh tokens.

Does the agent see my artist.tools password?

No. Authentication happens through the artist.tools OAuth flow in your browser. The AI client receives a limited MCP connection rather than your password.

Put Your artist.tools Workspace Inside Your AI Workflow

Search, investigate, compare, and organize music-industry data without rebuilding your artist.tools context in every conversation.

Connect an MCP client

Connect through OAuth. Revoke at any time.

Not ready for Developer Access yet? Compare artist.tools plans or explore everything artist.tools can do.