Ocoya has an MCP server, which lets an AI tool use Ocoya as a set of tools rather than you copying things back and forth. Connected, an assistant can draft and schedule posts, read your calendar, check channels and run workflows on your behalf.
It can also follow your AI campaigns, read your brand profile and brand score, and, if you are a brand owner or admin, update the brand’s description, website, tone of voice, guidelines, SEO keywords, hashtags and colors. If a connection you made earlier can’t update the brand, remove it and connect again.
Find it under Settings → MCP — Settings is in the account menu, the avatar at the top of the sidebar.
Start here. The account menu is the avatar at the top of the sidebar — Settings, then MCP in the settings sidebar.
Settings → MCP. Pick your app under MCP, follow its steps, and approve access when Ocoya opens.
Connect a tool
Under MCP in the settings sidebar, every app has its own page: Claude, ChatGPT, Gemini, Manus, Codex and VS Code. You can also pick one from Connect an app on the MCP page.
Each page walks you through connecting that app step by step, with the URL or command to copy at each step. Where an app connects in more than one way, a switch at the top picks it: Claude has Claude Desktop / Web, Claude Code and a JSON config, Gemini has Gemini CLI and settings.json, and Manus has a URL and an Import by JSON option.
The last step is always the same: Ocoya opens in your browser to approve the connection. Sign-in and brand approval are handled by OAuth — you don’t create or paste an API token for this.
At the foot of each page, Try it gives you a first thing to ask once it is connected — “List my Ocoya brands.” — which reads but changes nothing. Full guide opens that app’s page in the MCP documentation.
Step-by-step guides for each app: Claude, ChatGPT, Gemini, Manus, Codex and VS Code.
Approving access
When the tool connects, Ocoya shows a consent screen with Requested permissions and Select brands to allow.
Choosing brands here is the real decision. Unlike an API token — which always reaches every brand you own — an MCP connection is scoped to the brands you tick. If you run client brands, grant only the ones that tool should touch.
What a connected tool can do
The tools are grouped as Publishing, Campaigns, Planning, Creative assets, Channels, Workflows and Brands — roughly matching what you can do in the app yourself.
Anything that costs credits in Ocoya costs credits through MCP too. An assistant generating ten posts spends the same as you generating ten posts. See What are credits?
The full tool list is in the MCP documentation.
Managing connections
The MCP page lists every connected app with when it was connected, when its access expires, and which brands it can reach. Each app’s own page lists just its own connections.
Revoke access disconnects one immediately. Do that when you stop using a tool, when a connection covers brands it shouldn’t, or if a machine you connected from is no longer yours.
The MCP usage chart shows authenticated MCP requests for the current brand over the last hour, day or 30 days — useful for confirming a connection works, or noticing one that’s busier than expected.
API token or MCP?
| Use | |
|---|---|
| MCP | You want an AI assistant to work in Ocoya for you |
| API token | You’re writing code that calls Ocoya |
They’re separate mechanisms. Connecting a tool over MCP doesn’t need a token, and a token doesn’t grant MCP access.