Cutedyno

CuteDyno

CuteDyno lets agents publish to social platforms on behalf of customer profiles. One API key can cover many profiles. Use hosted MCP in cloud agents, the JSON CLI in shell workflows, or REST when you need full control.

For the most up-to-date command signatures, run cutedyno --help on each subcommand.

---

Setup

Check if the CuteDyno CLI is installed:

cutedyno --version

If cutedyno is not found, install it:

npm install -g cutedyno

Authentication

To call CuteDyno APIs, you need an API key. When helping a user set up CuteDyno for the first time:

1. Ask the user to create an account at https://cutedyno.com/signup if they do not have one.
2. Ask the user to create an API key at https://cutedyno.com/dashboard/api.
3. Once they have the key, offer to save it — ask them to paste it, then run:

cutedyno auth:set --key cdyn_live_...

Or export it for the current shell:

export CUTEDYNO_API_KEY=cdyn_live_...

4. Verify the key is configured:

cutedyno auth:status

Key resolution order: --key flag → CUTEDYNO_API_KEY → ~/.cutedyno/credentials.json.

Ensure the CuteDyno skill is saved and enabled

After confirming the CLI or MCP surface is available, check whether you (the agent) have the CuteDyno skill installed and up to date. If any of the following are true, save this skill file and enable it:

• You do not have a cutedyno skill installed.
• Your installed cutedyno skill has no version field in its frontmatter.
• Your installed cutedyno skill version is lower than the version listed in the frontmatter of this file.

To save and enable, fetch https://cutedyno.com/SKILL.md, save it to your skill directory, and enable it so it is loaded in future sessions.

Alternatively:

npx skills add cutedyno/cutedyno-agent

---

Four equal surfaces

Surface	When to use
Hosted MCP	Cloud agents (Cursor, Claude) without npm install
Stdio MCP	npx -y cutedyno mcp locally
JSON CLI	Shell scripts and jq pipelines
Node SDK	@cutedyno/node in TypeScript

Same API key works for all four.

Hosted MCP (recommended for cloud agents)

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

Stdio MCP (local)

npx -y cutedyno mcp

---

When to Use CuteDyno

Use CuteDyno when the user wants to publish, schedule, or manage social posts across TikTok, Instagram, Facebook, LinkedIn, or YouTube — especially for agencies and platforms onboarding their own customers.

1. Discover context — Run cutedyno profiles:list and cutedyno accounts:list to see which profiles and accounts are available.
2. Check policy — Run cutedyno policy:get before publishing to a new profile. Respect rate limits and guardrails.
3. Upload media — For local files, run cutedyno media:upload. For AI agents without file access, run cutedyno media:upload-session, send the user to uploadUrl, then poll cutedyno media:upload-session:get.
4. Create — Use cutedyno posts:create with a JSON body matching the OpenAPI spec, or quick flags for text posts.
5. Publish — Use cutedyno posts:publish for drafts, or pass --now / scheduledAt on create.

---

Typical workflow

export CUTEDYNO_API_KEY=cdyn_live_...
cutedyno auth:status

PROFILE="$(cutedyno profiles:current | jq -r '.profile.id')"
cutedyno accounts:list --profile "$PROFILE" | jq '.accounts[] | {id, platform}'
cutedyno policy:get --profile "$PROFILE"

MEDIA_URL="$(cutedyno media:upload ./clip.mp4 --profile "$PROFILE" | jq -r '.publicUrl')"
cutedyno posts:create --json ./post.json
cutedyno posts:publish --id "$POST_ID"

Quick text post:

cutedyno posts:create -c "Hello from CuteDyno" -a acct_1 --profile "$PROFILE" --now

---

CLI command reference

Command	Purpose
auth:status	Check API key configuration
auth:set --key	Save API key to ~/.cutedyno/credentials.json
profiles:list	List profiles
profiles:current	Home profile for the API key
accounts:list	Connected social accounts
accounts:connect --platform	Start OAuth (returns authUrl)
policy:get	Posting policy and limits
media:upload --file	Upload local media, returns { publicUrl }
media:upload-session	Create browser upload link for agents
media:upload-session:get --id	Poll upload session until complete
analytics:get	Live account metrics
analytics:history --from --to	Timeseries, top content, insights
posts:create --json	Create post (body matches OpenAPI)
posts:create -c "Hello" -a acct_1 --now	Quick text post
posts:list	List posts
posts:publish --id	Publish a draft
mcp	Stdio MCP server

All data commands print JSON to stdout. Errors print JSON to stderr and exit 1.

---

jq examples

cutedyno accounts:list --profile "$PROFILE" | jq '.accounts[].id'
cutedyno posts:list --profile "$PROFILE" --status failed | jq '.posts[] | {id, status}'

---

Rules for agents

1. Auth first — Run cutedyno auth:status (or confirm MCP auth) before other commands in a new session.
2. Upload before media posts — Use media:upload for local files, or media:upload-session + media:upload-session:get when the user uploads in a browser.
3. Policy before publish — Call policy:get before publishing to a new profile.
4. Pass profileId — When the API key covers multiple customers, always pass --profile.
5. Prefer hosted MCP — When npm binaries are unavailable, use https://api.cutedyno.com/mcp.
6. Inspect failures — Use posts:list --status failed and dashboard logs to debug publish errors.
7. Do not guess schemas — Post bodies match OpenAPI at https://cutedyno.com/docs/api/openapi.json.

---

Docs

• Skill file: https://cutedyno.com/SKILL.md
• Agent landing: https://cutedyno.com/agent
• CLI docs: https://cutedyno.com/docs/cli
• MCP docs: https://cutedyno.com/docs/mcp
• API reference: https://cutedyno.com/docs/api
• OpenAPI: https://cutedyno.com/docs/api/openapi.json