The Model Context Protocol (MCP) is an open standard that lets AI assistants use outside tools. Concerto runs a remote MCP server, so there is nothing to install: you add one URL to your assistant, sign in to Concerto, and choose what it may do. It is free on every plan.
The server address is:
https://mcp.concerto.studio/mcpIt uses Streamable HTTP and signs you in with OAuth, so any client that supports remote MCP servers with OAuth can connect. Your assistant only ever sees what your Concerto account can see.
How to connect
Every client below opens a Concerto page in your browser the first time it connects. Log in if you need to, check the app's name and where it will send you back to, choose its permissions and press Allow.
Claude (claude.ai, Claude Desktop and mobile)
- Go to Customize → Connectors, click + Add and choose Add custom connector.
- Name it
Concerto, enterhttps://mcp.concerto.studio/mcpas the URL and continue. Keep the detected OAuth sign-in settings, then click Add. - Approve the request in the Concerto window that opens.
- In a chat, click + → Connectors and switch Concerto on.
On Team and Enterprise plans, an owner first adds it under Organization settings → Connectors → Add → Custom → Web, then each member clicks Connect on it in Customize → Connectors. The free plan allows one custom connector.
ChatGPT (web)
- Open ChatGPT Plugins, click + and choose Add custom MCP server.
- Name it
Concerto. Under Connection, enterhttps://mcp.concerto.studio/mcpas the Server URL and choose OAuth for authentication. - Review the warning, select I understand and want to continue, then click Create as a plugin.
- Find Concerto in your personal or workspace plugins and install it.
- Approve the request in the Concerto window that opens.
- In a chat, type
@in the prompt box and select Concerto.
Your workspace's permissions and security settings control whether you can add and use custom MCP servers. Concerto supports both read and write tools, subject to the permissions you approve in Concerto.
ChatGPT desktop app
Open Settings → MCP servers → Add server. Name it Concerto, choose Streamable HTTP and enter https://mcp.concerto.studio/mcp. Save, select Restart, then click Authenticate to sign in and approve access in Concerto. The desktop app, Codex CLI and IDE extension share the same MCP configuration.
Claude Code
Add the server from your terminal:
claude mcp add --transport http concerto https://mcp.concerto.studio/mcpThen run /mcp inside Claude Code, pick concerto and choose to authenticate.
Codex
From the terminal, add the server and sign in:
codex mcp add concerto --url https://mcp.concerto.studio/mcp
codex mcp login concertoIn the Codex IDE extension, open the gear menu → MCP servers → Add server, choose Streamable HTTP, enter the URL, then click Authenticate. The CLI and the extension share the same configuration.
Claude Code and Codex can also upload audio from your computer, such as a bounce from your DAW project folder, because they can run the upload for you.
Other clients
Cursor, VS Code and any other client that supports remote MCP servers can connect with https://mcp.concerto.studio/mcp, using the Streamable HTTP transport and OAuth. The server publishes its OAuth metadata, so clients discover the sign-in flow on their own; there is no API key to copy.
Permissions
When you connect an app, Concerto shows you exactly what it is asking for. Each connection gets its own permissions, and you can change them by disconnecting and connecting again.
| Permission | Default | What it allows |
|---|---|---|
Readconcerto:read | Always on | See the workspaces, projects, songs, versions, comments, todos and stems you can already see, and fetch short-lived download links for audio. |
Writeconcerto:write | On by default | Post comments and replies, resolve comments, delete comments the app posted, create and tick off todos, upload new versions and start stem separation. Collaborators are notified exactly as if you had done it yourself. |
Shareconcerto:share | Off by default | Invite people to your projects, songs and versions, and turn public links on or off. Only granted if you tick it when connecting. |
Permissions never go beyond your own access. An agent can only comment where you can comment, and can only share what you could share yourself.
What agents can do
| Tool | Needs | What it does |
|---|---|---|
list_workspaces | Read | The workspaces you belong to. |
search | Read | Find projects, songs and versions by name, or from a Concerto link. |
get_project | Read | A project's songs and where each one stands. |
get_song | Read | A song's versions, todos and details. |
get_feedback | Read | Comments on a version with timestamps, replies and status: what's still open and who said it. |
get_activity | Read | What changed recently, for a digest across your work. |
get_audio_files | Read | Download links for a version and its stems. They expire after a few minutes. |
add_comments | Write | Time-synced comments and replies. |
set_comment_status | Write | Mark comments resolved or reopen them. |
delete_comments | Write | Take back comments the app posted for you, unless someone has replied. |
create_todos | Write | Turn feedback into a song's todo list. |
update_todos | Write | Tick todos off, or change them. |
start_version_upload | Write | Begin uploading a new version: returns a one-time upload link. |
finish_version_upload | Write | Finish the upload, with change notes and todos it fixes. |
split_stems | Write | Separate a version into stems (Ensemble and Symphony workspaces). |
share | Share | Invite someone to a project, song or version, or raise the access they already have. |
set_public_link | Share | Turn a version's public listening link on or off. |
What agents cannot do
- Delete your work. Apps can only delete comments they posted, and not once someone else has replied. There is no tool for deleting projects, songs, versions, todos, or comments written in the app. An agent can resolve a comment or mark a todo won't-do, and you can always undo that in the app.
- Touch billing, workspace membership or your account. Plans, seats, roles and account settings stay in the app.
- Share without permission. Inviting people and public links need the Share permission, which is off unless you tick it.
Audio files
Audio never travels through the conversation itself. To listen or analyse a mix, an agent asks for a download link that expires after a few minutes. To upload a new version, it gets a one-time upload link and sends the file straight to storage, which works in clients that can run commands on your computer, such as Claude Code and Codex. In chat apps like claude.ai and ChatGPT, the agent gives you a link to the song in Concerto so you can upload the file in your browser.
Collaborators can see what an agent did
Comments, replies, todos and versions an agent creates still show your name, followed by the app's, as in “Robert · via Claude”. Your collaborators know a note came through Claude rather than typed by hand, and are notified exactly as they would be for anything else you do.
Comments are written by other people, so Concerto tells agents to treat them as information and never as instructions. Leaving destructive actions out entirely is the stronger safeguard: a comment can't trick an agent into deleting your work, because no tool for that exists.
For workspace admins: read-only agents
In Workspace Settings → Agent Access, admins can turn on Connected apps can only read this workspace. Members can still connect their assistants and read what they can see, but commenting, uploading, changing todos and sharing fail for content in that workspace, with a message explaining why. Every member can see whether the switch is on; only admins can change it. Agent access can't be switched off entirely, because a connected app never sees more than its user already can in the browser.
How to disconnect
Open Settings → Connected apps in Concerto to see every app you have connected, what it may do and when it was last used. Press Disconnect and its access ends immediately; the app has to ask you again before it can reconnect. Removing the connector from your assistant's settings stops it trying, but disconnecting in Concerto is what revokes access.
Questions or a client that won't connect? Email info@archasolutions.com with the client you're using and what you saw.