Connect Velo to Claude

Before you start

You need a Velo account with at least one project. Every Claude product connects to the same address:

https://velo.meridianproject.studio/api/mcp

Velo signs you in through your browser. Never paste a Velo token or API key into Claude.

Claude on the web, Pro or Max

1. Go to Customize > Connectors.
2. Select +, then Add custom connector.
3. Enter the server URL above.
4. Leave Advanced settings blank. Velo recognizes Claude on its own, so there is no client ID or secret to enter.
5. Select Add, then Connect, and finish on Velo's consent screen.

Claude on the web, Team or Enterprise

An organization owner adds Velo once. Then each member connects their own account.

Owner, once

1. Go to Organization settings > Connectors.
2. Select Add, hover over Custom, and choose Web.
3. Enter the server URL above, leave Advanced settings blank, and select Add.

Each member

1. Go to Customize > Connectors.
2. Find Velo, labeled Custom, and select Connect.
3. Finish on Velo's consent screen, choosing your own projects.

Claude Desktop

Desktop uses the same connectors settings as the web. Add Velo from Connectors with the steps above, then finish on the consent screen in your browser. claude_desktop_config.json is only for local servers and isn't needed for Velo.

Claude on iOS and Android

Add Velo on the web or Desktop first. The mobile apps turn connectors you already have on or off, one conversation at a time.

1. In a conversation, tap +.
2. Tap Connectors.
3. Turn Velo on.

Claude Code

Add Velo from your terminal:

claude mcp add --transport http velo https://velo.meridianproject.studio/api/mcp

Then run /mcp inside Claude Code and choose Velo to sign in. Claude Code opens Velo's consent screen in your browser and returns to the terminal when you're done.

What Claude can see and do

Claude works only in the projects you pick when you connect, and only as far as your own role in each project allows.

It can read

• A summary of your workspace and the projects you picked.
• Their documents, versions, releases and review links.
• Feedback threads and every comment in them, by screen or by pinned element, with decisions and task status.
• Short-lived download links for captures and uploaded files.
• The progress of work it started, and the approval and audit records for it.

It can change, if you allow it

Changes need you to be an owner or editor of the project.

• Reply to feedback.
• Resolve, reopen or close a feedback thread.
• Create and update tasks on a thread.
• Ask reviewers to approve a release, once every thread in it is resolved or closed, or reopen approval of a release that was already approved.
• Queue a new version of a website by capturing its address again. The new version stays a draft until you publish it in Velo. Images and PDFs can't be recaptured this way.
• Assign, label and set the priority of feedback threads.
• Edit projects and documents, create releases and review links, and work through brand findings.

Each change is prepared first, then applied, and recorded with the connection that made it. Creating a release, capturing or uploading a document, and creating, extending or revoking a review link always wait for you to confirm them in Velo.

Claude can never approve a release for your client. Approving stays with the release's reviewers, through their own review link.

The choices on Velo's consent screen

When you connect, Velo opens its own consent screen in your browser. Nothing is shared until you select Approve connection. The top of the screen shows whether the app is a verified connector and where access goes.

Projects

Pick the organization, then the projects Claude can see. Every project starts ticked; untick any you want to keep out. Where it's offered, Include every current project in this organization covers the projects that exist today. New projects are not added later.

Let Claude make changes

On by default. Turn it off to connect read-only: Claude can then read the projects you picked, but can't post, change or delete anything.

Release approvals

Shown when changes are on. Confirm release approvals in Velo before they apply is the default: an approval request Claude prepares waits for you in Velo. The other choice lets Claude apply release approvals without asking. Feedback it reads could steer it, so choose that only for work you trust it with. Other protected changes, such as changing the address Velo captures a website from, always wait for you.

Confirming approvals and revoking access

Open Agent access in Velo to see every connection you've made.

• Approvals waiting on a connection are listed under it. Open one to review it, or use Confirm or Reject to decide every release approval shown at once. Any that need you to sign in again are skipped until you do. Other kinds of approval are reviewed one at a time.
• On a connection you made, switch between confirming release approvals yourself and letting them apply automatically. Switching cancels the approvals still waiting on that connection, so Claude prepares them again.
• Revoke access ends the connection and every token it holds. Then remove Velo from Customize > Connectors in Claude, or run /mcp in Claude Code and choose Clear authentication. Removing it only in Claude doesn't revoke access in Velo.

Limits

Velo limits how fast any connection can work, so a runaway conversation can't flood a project.

• At most 5 new website captures a day (UTC), counted per person in each organization. A capture that fails doesn't count.
• At most 60 threads resolved, reopened or closed an hour, per person in each organization.
• When a limit is reached, Velo tells Claude how long to wait. Reconnecting doesn't reset a limit.

Privacy

Velo receives the requests Claude makes and what it sends with them. It doesn't receive your conversation, memory or files.

Anthropic's own terms and privacy policy govern what Claude does with the work it reads. Velo can't recall data it has already sent.

How Velo handles data is in the privacy policy and the subprocessor registry.

Support

Email support@meridianproject.studio. Say which app you connected from and roughly when the problem happened. Never send a token or sign-in code.