MCP

MCP server

Expose CuteDyno to AI agents as MCP tools — same API, same permissions, same errors as REST.

CuteDyno MCP exposes the same API as tools. Agents can list accounts, upload media through a hosted browser page, create posts, read analytics, and check status without custom integration code. Tools come from the same registry as REST, so permissions and errors match /v1.

Hosted MCP endpoint

Recommended for Cursor, Claude, and cloud agents

No install
https://api.cutedyno.com/mcp

Authenticate with the same Bearer API key as REST. Create one under Developers → API.

Drop into Cursor or Claude MCP settings

{
  "mcpServers": {
    "cutedyno": {
      "url": "https://api.cutedyno.com/mcp",
      "headers": { "Authorization": "Bearer cdyn_live_..." }
    }
  }
}

Hosted HTTP

Point any MCP client at the URL above. Best for cloud agents and Cursor.

Stdio (local)

Spawn a local process when your runtime cannot call HTTP MCP.

npx -y cutedyno mcp

Tools

Tool detail pages are linked from this index (they are not listed in the sidebar).

Profiles

Accounts

Posts

Comments

Media

Analytics

Webhooks

Policy

Observability

Read-only tools are safe to auto-approve. Writes can publish to live accounts.

Resources and prompts

URIContents
cutedyno://docs/workflowHow to go from a connected account to a published post
cutedyno://docs/content-typesPayload shapes for text, image, and video posts
cutedyno://docs/errorsWhat each error code means and whether to retry
PromptWhat it doesArguments
draft-social-postWrite a post for one platform and create it as a draft in CuteDynoplatform, topic, tone?
weekly-content-planPlan a week of posts and create them as draftsthemes, platforms
audit-recent-activitySummarise what happened on a profile and flag failuresprofileId?

Guardrails

  1. Prefer a dedicated key per agent or environment so you can revoke one without taking everything down.
  2. Limit with profileIds, allowedAccountIds, and maxPostsPerDay when the caller is an LLM.
  3. Require human approval through profile policy — call get_policy or set requireApproval with PUT /v1/policy.

Troubleshooting

SymptomFix
No toolsConfig JSON invalid, or servers vs mcpServers mismatch. Run npx -y cutedyno mcp --tools with your API key set.
invalid_api_keyKey missing, revoked, or has stray whitespace.
insufficient_permissionKey lacks access for that action.
Unexpected draftsProfile requires approval. Call get_policy.
Local API failuresSet CUTEDYNO_API_URL (e.g. http://localhost:3000).