Model Context Protocol
CuteDyno MCP Server
The official MCP server for CuteDyno. Add it to Claude, Cursor, Codex, and other MCP-compatible tools to discover connected social pages, upload media, and schedule posts — without writing raw HTTP requests.
Create a CuteDyno API key, then follow the setup guide for your tool below. MCP access is included on paid plans alongside the REST API.
Get your API key
- Log in to CuteDyno on a paid plan.
- Go to Dashboard → API keys and create a new key.
- Copy the key (starts with
cdyn_live_). - Paste it into your MCP client config as shown below.
Tools
These tools map directly to the CuteDyno v1 REST API. Your agent calls them to manage posts and media on your behalf.
| Tool | Description |
|---|---|
| list_social_pages | List connected social pages. Use each page id as a targetId when creating posts. |
| list_posts | List posts with optional filters for state, content type, and platform. |
| get_post | Get full post detail including platform options and per-account overrides. |
| create_post | Create a draft, scheduled, or immediately queued post. |
| update_post | Edit a draft or scheduled post. |
| cancel_post | Cancel a scheduled or queued post. |
| get_upload_signed_url | Get a presigned URL for uploading images or videos before creating a post. |
Resources & prompts
Resources
cutedyno://docs/workflow— Step-by-step scheduling workflowcutedyno://docs/content-types— Text, image, and video payload shapes
Prompts
draft-social-post— Draft a post for a platform and create it via the APIweekly-content-plan— Plan and draft a week of content across platforms
Cursor
- Create an API key from your CuteDyno dashboard (Settings → API).
- Open your MCP config at ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project.
- Add the CuteDyno server configuration below.
- Save the file. Cursor picks up changes automatically.
- Start a chat and ask your agent to list your connected social pages.
{
"mcpServers": {
"cutedyno": {
"command": "npx",
"args": ["-y", "cutedyno-mcp"],
"env": {
"CUTEDYNO_API_KEY": "cdyn_live_YOUR_KEY"
}
}
}
}Claude Desktop
- Create an API key from your CuteDyno dashboard.
- Open Claude Desktop → Settings → Developer → Edit Config.
- On macOS the file is ~/Library/Application Support/Claude/claude_desktop_config.json.
- Add the mcpServers block below inside the root JSON object.
- Restart Claude Desktop completely, then look for the tools icon below the chat input.
{
"mcpServers": {
"cutedyno": {
"command": "npx",
"args": ["-y", "cutedyno-mcp"],
"env": {
"CUTEDYNO_API_KEY": "cdyn_live_YOUR_KEY"
}
}
}
}Claude Desktop requires a full restart after saving the config file.
Claude Code
- Install the Claude Code CLI: npm install -g @anthropic-ai/claude-code
- Add the CuteDyno MCP server (user scope works across all projects):
claude mcp add cutedyno --transport stdio --scope user -- npx -y cutedyno-mcpSet CUTEDYNO_API_KEY in your shell environment, or add --env CUTEDYNO_API_KEY=cdyn_live_... to the command. Run /mcp in Claude Code to verify the connection.
Remote (Streamable HTTP)
- Use the hosted MCP endpoint if your client supports remote servers with Bearer auth.
- No local npx process required — your client connects directly to the CuteDyno API.
- Add the configuration below to your client MCP settings.
{
"mcpServers": {
"cutedyno": {
"url": "https://api.cutedyno.com/mcp",
"headers": {
"Authorization": "Bearer cdyn_live_YOUR_KEY"
}
}
}
}Endpoint: POST https://api.cutedyno.com/mcp with Authorization: Bearer cdyn_live_...
https://api.cutedyno.com/mcp
OpenAI Codex CLI
- Install: npm install -g @openai/codex@latest
- Add the CuteDyno MCP server:
codex mcp add cutedyno --env CUTEDYNO_API_KEY=cdyn_live_YOUR_KEY -- npx -y cutedyno-mcpRun codex, then type /mcp to verify tools like list_social_pages and create_post are available.
Windsurf
- Edit ~/.codeium/windsurf/mcp_config.json
- Add the configuration below.
{
"mcpServers": {
"cutedyno": {
"command": "npx",
"args": ["-y", "cutedyno-mcp"],
"env": {
"CUTEDYNO_API_KEY": "cdyn_live_YOUR_KEY"
}
}
}
}Built with the MCP TypeScript SDK. See also the REST API reference for raw HTTP endpoints.