For local agent tooling
AI Agents CLI for social media scheduling
The Creagency CLI and stdio MCP server let agents inspect connected accounts, create drafts, upload media, and prepare publish actions from the terminal without exposing platform passwords.
Published as @creagency/agent with creagency and creagency-mcp binaries for local workflows.
Verify the workspace
Check the API key and connected accounts before asking any agent to create content.
Prompt
Run creagency auth:status --json and creagency integrations:list --json. Summarize which social accounts are available.Scoped API key
Draft first
Confirmed publish
Quick start
Get CLI working with Creagency.
Give every local agent one social media command surface.
1
Create a scoped Creagency API key
Use a key with post, asset, and integration scopes. The agent should not receive your social platform passwords.
2
Install the local tooling
Install @creagency/agent, export CREAGENCY_API_KEY, and verify the workspace with auth:status and integrations:list.
3
Add the Creagency skill
Give the agent the Creagency API rules so it knows account discovery, media upload, draft creation, and publish confirmation.
4
Run the first draft
Ask for a draft and require the agent to show the connected account and post summary before scheduling or publishing.
Setup
Use the surface that matches how CLI runs.
Skill files teach the rules, CLI commands handle terminal workflows, and local stdio MCP gives supported agent clients bounded tools.
Skill
Install the Creagency skill so your agent uses the real API rules instead of inventing endpoints.
Steps
Install the skill file in the agent's supported skill directory.
Tell the agent to read the skill before it drafts, uploads media, or prepares publish actions.
Keep API keys outside prompts and chat transcripts.
Install the Creagency skill
Use this for agents that read local skill files.
mkdir -p ~/.agents/skills/creagency-api
curl -fsSL https://creagency.ai/.agents/skills/creagency-api/SKILL.md \
-o ~/.agents/skills/creagency-api/SKILL.mdCLI
Use parseable terminal commands when the agent can run local shell tools.
Steps
Install @creagency/agent globally or call it with npx.
Set CREAGENCY_API_KEY and CREAGENCY_API_ORIGIN in the shell or agent environment.
Run auth:status and integrations:list before creating a post.
Creagency CLI baseline
Start every local agent setup with an auth check and account discovery.
npm install -g @creagency/agent
export CREAGENCY_API_KEY=creagency_xxx
export CREAGENCY_API_ORIGIN=https://api.creagency.ai
creagency auth:status --json
creagency integrations:list --jsonLocal MCP
Run creagency-mcp as a local stdio server so your agent can use bounded Creagency tools. Hosted remote MCP is planned as a separate OAuth-based connector. Use the local CLI and stdio MCP server today.
Steps
Point the agent client at the creagency-mcp stdio command.
Pass CREAGENCY_API_KEY through the environment rather than inline config.
Use prepare tools for publish and delete, then require the returned confirmation token.
your agent MCP server entry
This launches the local Creagency stdio MCP server.
{
"mcpServers": {
"creagency": {
"command": "npx",
"args": ["-y", "-p", "@creagency/agent", "creagency-mcp"],
"env": {
"CREAGENCY_API_ORIGIN": "https://api.creagency.ai"
}
}
}
}Publish flow
Publish and delete require target-bound confirmation. --confirm true is intentionally rejected.
Steps
Prepare the content as a draft first.
Show the target post id and summary to the user.
Publish only when --confirm matches the post id.
Guarded publish command
creagency posts:create --file post.json --json
creagency media:upload ./launch-card.png --category assets --json
creagency posts:publish post_123 --confirm post_123 --jsonExamples
CLI prompts you can actually use.
Verify the workspace
Check the API key and connected accounts before asking any agent to create content.
Prompt
Run creagency auth:status --json and creagency integrations:list --json. Summarize which social accounts are available.Expected outcome
A clean readiness report with account ids, platform names, and no leaked API key.
Create a draft from a file
Use the CLI when a local process has already prepared a JSON payload.
Prompt
Create a Creagency draft from ./post.json, return the post id, and do not publish.Expected outcome
A draft exists in Creagency and the agent reports the post id for review.
Upload media before drafting
Send a local image through the signed upload flow, then attach it to the draft.
Prompt
Upload ./launch-card.png with Creagency, then create a LinkedIn draft that uses the uploaded asset.Expected outcome
An asset is stored in Creagency and linked to a review-ready post draft.
Prepare a publish action
Use the confirmation flow when a person asks the agent to publish.
Prompt
Prepare post_123 for publish, show me the summary, and wait for my confirmation.Expected outcome
The agent returns the summary and does not execute publish until confirmation is provided.
Safety
Keep the agent useful without handing over your channels.
Read connected accounts before creating or scheduling content.
Keep API keys in environment variables and never print them in chat.
Create drafts first when the user has not explicitly asked to schedule.
Prepare publish and delete actions before execution, then ask for confirmation.
Troubleshooting
When the first run does not work.
the CLI agent cannot see connected accounts.
Run creagency auth:status --json, then integrations:list --json. If the list is empty, connect social accounts in Creagency first.
A post command fails with a missing scope.
Create or rotate the API key with posts:read, posts:write, assets:read, assets:write, and integrations:read.
The agent tries to publish immediately.
Point it back to the skill rule: create or schedule a draft first unless the user explicitly confirms publish.
FAQ
What CLI users usually ask first.
Can the agent publish without approval?
Creagency local MCP publish and delete flows are two-step. The agent prepares the action, shows the summary, and only executes after confirmation.
Is hosted remote MCP available now?
Not generally. The available path is the local CLI and stdio MCP package. Hosted remote MCP with OAuth is planned separately.
Does the agent need social account passwords?
No. Social channels connect through Creagency and platform OAuth. Agents use scoped Creagency API keys.
Set up AI Agents CLI with Creagency.
Install the skill, connect the CLI or local MCP server, and start with one draft that your team can review.