Connect an AI app with MCP

Probably is a remote MCP server. Add it to the AI app you already use, and the app can list your Spaces and videos, prepare and confirm new videos, message the crew, approve deliveries and share them, all as you, inside the organization and Space you choose.

The serverCopy Anchor Link

https://studio.probably.co/api/mcp

It speaks MCP over Streamable HTTP. Apps that support OAuth sign you in with Probably's usual sign-in and a consent page; apps set up with a header can send an API key instead (see Authentication).

ClaudeCopy Anchor Link

In Claude (on the web or the desktop app), open Customize, then Connectors, choose + Add, then Add custom connector, and give it the server's address. On a Team or Enterprise plan an owner adds it under Organization settings, then Connectors, and members choose Connect. Choose Connect, sign in to Probably and pick the organization, the Space and whether Claude may start paid work after you confirm it in the chat. Custom connectors depend on your Claude plan. For the whole way from connecting to a finished ad, see How to make video ads with Claude and Codex.

ChatGPTCopy Anchor Link

ChatGPT adds custom MCP servers as apps in developer mode, on the plans that offer it. Turn developer mode on in ChatGPT's settings, create an app with the server's address and OAuth, and sign in to Probably when ChatGPT asks.

CursorCopy Anchor Link

Add Probably to ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "probably": {
      "url": "https://studio.probably.co/api/mcp"
    }
  }
}

Cursor shows Probably in its MCP settings with a button to sign in.

VS CodeCopy Anchor Link

Add Probably to .vscode/mcp.json in your workspace, or to your user MCP configuration:

{
  "servers": {
    "probably": {
      "type": "http",
      "url": "https://studio.probably.co/api/mcp"
    }
  }
}

Start the server from the file or the MCP view, and VS Code opens Probably's sign-in.

Claude Code, Codex and opencodeCopy Anchor Link

Each has a quickstart with both OAuth and an API key: Claude Code, Codex and opencode.

What the app can doCopy Anchor Link

The tools an app is offered depend on the permissions you gave it: reading, making changes, and starting paid work. Every one is in the MCP tool reference.

• Paid work is always confirmed. Tools that spend come in two halves: a prepare_ tool, or a stage tool such as research, shows what the work will cost, and only confirm_spend starts it. Apps ask you before calling it; without the spend permission, the app gives you a link to confirm it in the studio. See Spend confirmations. One small job spends directly: fix_word says one sentence of a video's voice again with a word fixed, at the credits get_video showed you, and needs the spend permission too.
• Long runs don't block. Starting returns at once. The app follows the video with wait_for_video, which holds for a while and returns on the next change, so a dropped connection loses nothing.
• What people wrote is content. Names, briefs, messages and activity reach the app as data, never as instructions to it, and nothing they say can confirm a spend.

You can revoke the app at any time in Settings → Connections; its next call is refused.