Skip to main content

​
Connect AI tools to Ocoya

Open MCP settings Ocoya MCP lets AI clients work with your Ocoya account through approved, workspace-scoped access. After you connect a client, it can inspect workspaces, list social profiles, draft posts, schedule posts, publish immediately, manage brand kits, and run workflows on your behalf. Use MCP when you want an assistant such as Claude, Codex, Cursor, VS Code, or another MCP-compatible client to perform Ocoya actions directly instead of giving it API keys or asking it to generate REST calls.

Workspace-aware

The OAuth approval screen lets you choose which Ocoya workspaces the client can access.

No API keys

MCP uses OAuth. Ocoya API keys are not accepted by the MCP server.

Read and write tools

Clients can discover content, create posts, schedule posts, publish posts, and run workflows.

Structured results

Tool responses include JSON-friendly structuredContent for clients that can consume it.

​
Endpoint

https://mcp.ocoya.com
The endpoint accepts JSON-RPC 2.0 requests over HTTP POST. It supports single requests and JSON-RPC batch requests. If your environment has not moved to the MCP subdomain yet, use: 
https://app.ocoya.com/api/mcp

​
Authentication

Ocoya MCP uses OAuth. No Ocoya API key is required, and API keys are not accepted by the MCP server. When a client first uses an Ocoya tool, it opens Ocoya in the browser. The user signs in, reviews the requested permissions, selects allowed workspaces, and approves access. The client receives a short-lived access token and can refresh it according to the OAuth flow. Approved grants can include these capabilities:
CapabilityWhat it allows
workspace:readRead approved workspaces and brand kits.
social_profiles:readRead connected social profiles in approved workspaces.
posts:readList, inspect, and preview posts.
posts:writeCreate drafts, update posts, schedule posts, and delete posts.
posts:publishPublish posts immediately.
workflows:readList and inspect workflows.
workflows:runToggle workflows and queue workflow runs.

​
Client configuration

claude mcp add ocoya --transport http https://mcp.ocoya.com
Add a custom connector and paste the MCP URL:
https://mcp.ocoya.com

[mcp_servers.ocoya]
url = "https://mcp.ocoya.com"

{
  "mcpServers": {
    "ocoya": {
      "url": "https://mcp.ocoya.com"
    }
  }
}

{
  "servers": {
    "ocoya": {
      "type": "http",
      "url": "https://mcp.ocoya.com"
    }
  }
}
Client configuration formats differ. If your client asks for a transport, choose HTTP or streamable HTTP and use the endpoint above.

​
Typical flow

1

Add the MCP server

Configure your MCP-compatible client with https://mcp.ocoya.com.
2

Approve OAuth access

Ocoya opens in the browser. Sign in, review permissions, select the workspaces the client may access, and approve the connection.
3

Resolve workspace and profile IDs

Ask the client to list workspaces and social profiles before creating or scheduling posts.
4

Ask for the Ocoya action

The client can call Ocoya tools to draft, schedule, publish, update, delete, or inspect content.

​
Useful prompts

Use natural language. The client decides which MCP tools to call. 
List my Ocoya workspaces and show the connected social profiles in the Acme workspace.

Create a draft post in Acme with this caption: "Our summer launch is live."

Schedule that post for LinkedIn tomorrow at 09:00 in the workspace timezone.

Show me workflows in Acme and run the product launch workflow with campaignId set to summer-2026.

​
Manual protocol check

Most users should let their MCP client handle OAuth and JSON-RPC. For diagnostics, an unauthenticated request should return 401 with a WWW-Authenticate header that points to Ocoya OAuth metadata. 
curl -i https://mcp.ocoya.com \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'
After OAuth, clients call tools through tools/call: 
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "ocoya_list_workspaces",
    "arguments": {}
  }
}

​
Troubleshooting

IssueWhat to check
401 responseThe client has not completed OAuth, the access token expired, or the client is using an API key instead of OAuth.
Workspace not foundThe workspace was not selected during approval, or the client is using an ID from a different Ocoya account.
Social profile rejectedUse ocoya_list_social_profiles for the same workspace and pass one of the returned IDs.
Invalid scheduleUse an ISO datetime such as 2026-07-01T09:00:00Z.
Workflow cannot be toggledResolve validation errors in the workflow before enabling or disabling it.

​
Safety

Only approve MCP clients you trust. MCP clients can perform write actions in the workspaces you allow, including creating posts, scheduling posts, publishing posts, deleting posts, toggling workflows, and running workflows. Review the client action before approving sensitive tasks such as immediate publishing or deletion.

​
Next

MCP tools

Review every Ocoya MCP tool, required argument, and common usage pattern.