Connector guide

Connect Velo to ChatGPT

Give ChatGPT access to the Velo projects you choose, so it can summarize client feedback, close the loop on threads and move a release toward approval.

Before you start

You need a Velo account with at least one project, and a ChatGPT Plus, Pro, Business, Enterprise or Education plan. ChatGPT connects to this address:

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

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

Turn on developer mode

  1. Open ChatGPT Settings.
  2. Go to Security and login. Some accounts show this under Connectors instead.
  3. Turn on Developer mode.

Add Velo

  1. Open Settings > Connectors, or the + button in a chat, depending on your account.
  2. Create a new connector for a remote MCP server.
  3. Enter the server URL above.
  4. For authentication, choose OAuth. Velo refuses connections without it. Leave any client ID and secret fields blank unless ChatGPT insists.
  5. Save. ChatGPT sends you to Velo's consent screen to finish.
  6. Velo then appears under Drafts in your connector settings. From there you can turn single tools off, or refresh to pick up changes to Velo's tools.

These steps were checked against OpenAI's developer-mode guide on 23 September 2026. If a menu has moved, the server URL and consent screen stay the same.

What ChatGPT can see and do

ChatGPT 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.

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

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 ChatGPT 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 ChatGPT make changes
On by default. Turn it off to connect read-only: ChatGPT 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 ChatGPT prepares waits for you in Velo. The other choice lets ChatGPT 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 ChatGPT prepares them again.
  • Revoke access ends the connection and every token it holds. Then remove or turn off the connector in ChatGPT, so it stops trying to reconnect.

Limits

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

Requests per minute
WorkEach connectionYou, across connections
Reading120300
Preparing a change3060
Applying a change, approval steps and new captures1020
  • 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 ChatGPT how long to wait. Reconnecting doesn't reset a limit.

Privacy

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

OpenAI's own terms and privacy policy govern what ChatGPT 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.