For codebase-aware agents
Social media scheduling for Claude Code
Use Creagency when Claude Code needs to move from implementation context to social drafts while keeping social account control in your workspace.
Works with scoped API keys, skill instructions, Claude MCP config, and draft-first publishing.
Feature branch to launch copy
Claude Code reads the branch context, drafts a post, and leaves it for review.
Prompt
Use Creagency to draft a LinkedIn post from this feature branch. Show the draft and do not schedule it yet.Scoped API key
Draft first
Confirmed publish
Quick start
Get Claude working with Creagency.
Claude Code can explain the work and draft the announcement.
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 Claude 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 Claude Code 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
Add creagency-mcp with Claude Code's MCP command or project config. Hosted remote MCP is planned as a separate OAuth-based connector. Use the local CLI and stdio MCP server today.
Steps
Use claude mcp add for a local stdio server.
Set CREAGENCY_API_KEY in the environment, not the prompt.
Approve the project MCP server in Claude Code before expecting tool calls.
Claude Code MCP command
claude mcp add creagency -- npx -y -p @creagency/agent creagency-mcpExamples
Claude prompts you can actually use.
Feature branch to launch copy
Claude Code reads the branch context, drafts a post, and leaves it for review.
Prompt
Use Creagency to draft a LinkedIn post from this feature branch. Show the draft and do not schedule it yet.Expected outcome
A review-ready LinkedIn draft is created from code and docs context.
Issue summary to social update
Claude turns a closed issue into a customer-facing update.
Prompt
Summarize the closed issue and create one X draft in Creagency. Keep the tone plain and specific.Expected outcome
A short post draft is created without leaking internal issue details.
Docs guide launch
Claude Code converts a new guide into multiple channel drafts.
Prompt
Create a LinkedIn post and an X post from docs/api/agent-playbook.md. List accounts first.Expected outcome
Two drafts exist in Creagency and the selected accounts are visible for review.
Media attachment check
Claude uploads a local screenshot and links it to a post.
Prompt
Upload ./screenshots/new-dashboard.png to Creagency, attach it to a LinkedIn draft, and stop before publish.Expected outcome
The draft includes the uploaded image and waits for approval.
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.
Claude Code 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 Claude 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 Claude Code with Creagency.
Install the skill, connect the CLI or local MCP server, and start with one draft that your team can review.