Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.patchline.ai/llms.txt

Use this file to discover all available pages before exploring further.

Pick your client. Each install is one config snippet or one command — about 30 seconds. Authentication runs the first time you make a tool call (browser-based OAuth 2.0 with PKCE).   Free to install on every tier. Tool calls consume your AI credit pool.

​
The endpoint

For every client, the URL is the same: 
https://www.patchline.ai/api/mcp/v1

​
Cursor

1

Open Cursor settings

Cmd / Ctrl + , → MCP in the sidebar → + Add new MCP server.
2

Paste the config

{
  "mcpServers": {
    "aria": {
      "url": "https://www.patchline.ai/api/mcp/v1"
    }
  }
}
3

Authenticate on first call

The first tool call opens a browser to patchline.ai. Sign in (or Google OAuth), approve the connection, return to Cursor. You’re set.
1-click install: open this URL on the same machine running Cursor — it triggers Cursor’s MCP deeplink installer: 
cursor://anysphere.cursor-deeplink/mcp/install?name=aria&config=eyJhcmlhIjp7InVybCI6Imh0dHBzOi8vd3d3LnBhdGNobGluZS5haS9hcGkvbWNwL3YxIn19
Or use the “Install in Cursor” button at the top of any page in these docs (via the contextual menu).

​
Codex

1

Enable remote MCP

In ~/.codex/config.toml, set:
experimental_use_rmcp_client = true
2

Add the server

codex mcp add aria --url https://www.patchline.ai/api/mcp/v1
3

Authenticate on first call

Codex opens the browser, you sign in to Patchline, return to Codex. Tokens cached locally.

​
VS Code (with Copilot or any MCP-aware extension)

1

Create or edit .vscode/mcp.json

In your workspace root, create .vscode/mcp.json (or merge with an existing one):
{
  "servers": {
    "aria": {
      "type": "http",
      "url": "https://www.patchline.ai/api/mcp/v1"
    }
  }
}
2

Reload VS Code

Reload the window so the extension picks up the new server.
3

Authenticate on first call

Same browser-based OAuth flow.
Alternate: if your extension doesn’t support direct HTTP transport, use mcp-remote to bridge: 
{
  "servers": {
    "aria": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.patchline.ai/api/mcp/v1"]
    }
  }
}

​
Claude Desktop

1

Open Claude Desktop config

Settings → Developer → Edit Config. Opens claude_desktop_config.json.
2

Add the Patchline server

{
  "mcpServers": {
    "aria": {
      "url": "https://www.patchline.ai/api/mcp/v1",
      "transport": "http"
    }
  }
}
3

Restart Claude Desktop

Quit and relaunch. Aria appears in the connectors list.
4

Authenticate on first call

Browser-based OAuth.
Recommended for Claude users: use the official Patchline Claude plugin instead. It wraps the same MCP server with a progressive-interview workflow built for music release planning.

​
Claude Code

Claude Code has its own plugin command. Three steps:
1

Add the marketplace

/plugin marketplace add Patchline-AI/aria
2

Install the plugin

/plugin install aria@patchline-ai
/reload-plugins
3

Authenticate

Run:
/mcp
Then authenticate plugin:aria:aria. Browser OAuth opens.
This is the recommended path for Claude Code. The plugin ships with extra context: progressive interview workflow, lifecycle phase skills, and Patchline-specific slash commands.

​
ChatGPT / OpenAI ChatGPT app

ChatGPT’s MCP support is in early access at time of writing. When it lands publicly, point ChatGPT’s MCP config at https://www.patchline.ai/api/mcp/v1 with the same OAuth flow as the other clients.

​
Any other MCP-compatible client

Patchline implements the MCP spec version 2025-03-26. Any compliant client should work with this config shape: 
{
  "name": "aria",
  "transport": "http",
  "url": "https://www.patchline.ai/api/mcp/v1"
}
OAuth discovery is at /.well-known/oauth-protected-resource per RFC 9728.

​
Verify your install

After authenticating, ask your AI: 
What MCP tools do you have available?
You should see the 18 Patchline tools listed (or a count of 18+). If you see them, you’re connected. Test a real call: 
Paste a Spotify URL → AI calls analyze_url → returns track identity.
If the first call fails with unauthenticated, your client may have skipped the OAuth flow — disconnect and reconnect, the browser should open.

​
Pricing

TierInstallTool call cost
All tiersFreeCounts against your AI credit pool
A typical user spends 200–500 credits/month via MCP. The MCP server itself is free; only the underlying tool calls consume credits. See Plans & credits.

​
Troubleshooting

Most likely the URL is missing https:// or has a trailing slash. The correct value is exactly https://www.patchline.ai/api/mcp/v1 — no trailing /.
Check the URL the browser opened — it should be https://patchline.ai/api/mcp/v1/authorize?.... If you saw a localhost: URL, your client is using loopback callback and got blocked by a firewall. Try a different network or check firewall settings.
Tier-gated tool. find_playlists and inspect_playlist require Pro+. Upgrade or use a different tool.
Your client’s redirect URI isn’t registered with Patchline. Email support@patchline.ai with the URI your client uses — we’ll add it.
Patchline Settings → Security → Connected applications → revoke Aria MCP. Next call from the client will re-prompt OAuth.
Yes — they’re separate servers with separate names. Most users install both: docs MCP for learning Patchline, product MCP for acting on data. See MCP overview for the distinction.