Agent setup

Set up Creagency with Codex

Point Codex at the Creagency skill, CLI, or local MCP server so it can list accounts, create drafts, upload media, and stop before publish.

Open landing page Read Creagency skill guide

Quick start

Step 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.

Step 2

Install the local tooling

Install @creagency/agent, export CREAGENCY_API_KEY, and verify the workspace with auth:status and integrations:list.

Step 3

Add the Creagency skill

Give the agent the Creagency API rules so it knows account discovery, media upload, draft creation, and publish confirmation.

Step 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 surfaces

Skill

Install the Creagency skill so Codex uses the real API rules instead of inventing endpoints.

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.md

Open docs

CLI

Use parseable terminal commands when the agent can run local shell tools.

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 --json

Open docs

Local MCP

Run creagency-mcp as a local stdio server so Codex 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.

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.

Codex MCP server entry

This launches the local Creagency stdio MCP server.

[mcp_servers.creagency]
command = "npx"
args = ["-y", "-p", "@creagency/agent", "creagency-mcp"]

[mcp_servers.creagency.env]
CREAGENCY_API_ORIGIN = "https://api.creagency.ai"

Open docs

Prompt examples

Changelog to LinkedIn and X

Codex reads local release notes, then creates channel-specific drafts.

Prompt

Use Creagency to draft a LinkedIn post and an X post from CHANGELOG.md. List connected accounts first and do not publish.

Expected outcome

Two Creagency drafts are created with copy tailored to each channel.

Launch image upload

Codex uploads local media and attaches it to a draft.

Prompt

Upload ./assets/launch-card.png to Creagency, then attach it to a LinkedIn draft about this release.

Expected outcome

The media asset is stored and linked to the draft without exposing the signed upload URL.

Docs announcement

Codex summarizes a documentation change into a social post.

Prompt

Read docs/api/agent-playbook.md and create one Creagency draft announcing the guide. Keep it under 900 characters.

Expected outcome

A concise post draft references the guide without publishing.

Publish review

Codex prepares publish only after a human asks for it.

Prompt

Prepare post_123 for publishing and show me the final text, platform, account, and schedule before executing.

Expected outcome

Codex returns a publish summary and waits for confirmation.

Safety rules

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

Codex 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.

Sources

Codex CLI featuresOpen

Codex configuration referenceOpen

Creagency Agent READMEOpen

Creagency skill docsOpen