The DropTrack MCP server lets supported AI assistants connect securely to your DropTrack account. After setup, your assistant can help you review tracks, campaigns, contacts, playlists, assets, AI jobs, ad campaigns, label activity, artist profile context, and account details with plain-language prompts.
This article is the setup guide. For examples of what to ask once you are connected, see MCP Workflows: What to Try First.
Before You Start
- You need a DropTrack account.
- Use the DropTrack production MCP URL:
https://mcp.droptrack.com/mcp
- The first connection opens a DropTrack sign-in flow.
- Sign in with the DropTrack account you want the assistant to access.
- The assistant is scoped to the DropTrack company or account available to that login.
- If you manage multiple companies, ask the assistant to list them and switch context.
What Your Assistant Can Access
Available tools depend on your DropTrack permissions.
- Tracks, track versions, analytics, downloads, and timestamped comments.
- Campaign lists, campaign details, campaign analytics, and draft campaign creation.
- Contacts, contact lists, contact creation, and adding contacts to lists.
- Playlists and playlist details.
- Uploaded or AI-generated images and uploaded documents.
- AI workflows for press releases, artist bios, album art, audio analysis, track tagging, and submission opportunities.
- Grow and ads campaigns, ads analytics, wallet balance, and wallet transactions.
- Label-wide analytics, roster contacts, team access, ads data, and shared wallet settings when your account has label management access.
- Artist profile context used by the AI artist bio feature.
If a tool is missing, your client may need a refresh, or your DropTrack account may not have permission for that feature.
VS Code and GitHub Copilot
VS Code supports MCP servers through GitHub Copilot Agent mode.
- Open VS Code.
- Open the Command Palette.
- Run MCP: Add Server.
- Choose an HTTP server and enter:
https://mcp.droptrack.com/mcp
- Name the server droptrack.
- Run MCP: List Servers and start the DropTrack server.
- When prompted, complete the DropTrack sign-in flow in your browser.
- Use GitHub Copilot in Agent mode and ask for DropTrack data, such as
List my DropTrack playlists.
You can also create a workspace config at .vscode/mcp.json:
{
"servers": {
"droptrack": {
"type": "http",
"url": "https://mcp.droptrack.com/mcp"
}
}
}
If tools do not appear after a DropTrack MCP update, run MCP: Reset Cached Tools in VS Code, then reconnect.
Cursor
Cursor reads MCP configuration from an mcp.json file.
- Create
.cursor/mcp.jsonin your project, or~/.cursor/mcp.jsonfor a global setup. - Add this configuration:
{
"mcpServers": {
"droptrack": {
"url": "https://mcp.droptrack.com/mcp"
}
}
}
- Restart Cursor or refresh MCP tools from Cursor settings.
- When Cursor prompts you to authenticate, sign in to DropTrack in the browser.
- Use Cursor Agent and ask for DropTrack data, such as
Show my latest campaign performance.
Claude Code
Claude Code can add the DropTrack MCP server from the terminal.
- Open a terminal in the project where you want to use DropTrack.
- Run:
claude mcp add --transport http droptrack https://mcp.droptrack.com/mcp
- To make it available across projects, add
--scope user. To save it only for the current project, add--scope project. - Inside Claude Code, run
/mcp. - Authenticate with DropTrack in the browser and verify that the DropTrack tools are listed.
ChatGPT
ChatGPT can connect to remote MCP servers through custom connectors when that feature is available for your plan or workspace.
- Open ChatGPT settings.
- Go to Connectors.
- If needed, enable Developer mode under advanced connector settings.
- Create or import a custom connector or app for a remote MCP server.
- Use this server URL:
https://mcp.droptrack.com/mcp
- Complete the DropTrack OAuth sign-in flow.
- In a chat, enable or select the DropTrack connector before asking for DropTrack data.
If you do not see options for custom connectors, remote MCP servers, or developer mode, your ChatGPT plan or workspace may not currently allow custom MCP connectors.
OpenAI Codex
If you use Codex with MCP support, add the DropTrack server from the command line:
codex mcp add droptrack --url https://mcp.droptrack.com/mcp
Then verify it is configured:
codex mcp list
When Codex first uses the server, complete the DropTrack sign-in flow in your browser.
How Authentication and Account Scope Work
- The MCP server uses DropTrack sign-in to confirm who you are.
- Your assistant is scoped to the DropTrack company or account available to your login.
- If you have access to multiple companies, ask:
List my DropTrack companies, then ask the assistant to switch to the company you want. - Label-wide tools require the correct label permissions.
- Write tools are limited to safe actions such as creating drafts, creating contact lists, adding contacts to lists, queueing AI jobs, and saving generated assets.
Quick Test Prompts
After setup, try one of these:
List my DropTrack playlists.
Show my latest campaign performance.
Show comments for this track, grouped by timestamp and theme.
Create a new contact list called "Blog Press".
Check my ads wallet and active campaign performance.
List my available DropTrack companies and switch to the artist account I choose.
Troubleshooting
- Tools do not appear: Refresh MCP tools, restart the client, or reset cached tools if your client supports it.
- New tools are missing after an update: Reset cached tools and reconnect so your client can fetch the latest catalog.
- Authentication failed: Disconnect the DropTrack MCP server and reconnect so the browser sign-in flow starts again.
- Wrong account data: Make sure you signed in with the intended DropTrack account. If you manage multiple companies, ask the assistant to list companies and switch context.
- Permission errors: Some tools require label access, ads feature access, or plan access.
- Still stuck: Contact DropTrack support and include the MCP client you are using, the server URL, and the error message shown by the client.
What To Try Next
Once connected, see MCP Workflows: What to Try First for practical examples covering tracks, campaign follow-up, contact lists, playlists, AI workflows, label reporting, and ads health.