Agent setup

Set up Creagency with Perplexity Computer

Use Creagency as the action layer after research: pick channels, create drafts, attach media, and let a person approve publishing.

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

Perplexity 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"
      }
    }
  }
}

Open docs

Prompt examples

Research-backed campaign

Turn a research summary into several social drafts.

Prompt

Use Creagency to draft three posts from this research summary: one LinkedIn post and two X posts. Keep all claims tied to the source notes.

Expected outcome

Three drafts are created with source-aware wording.

Content calendar fill

Convert research angles into a week of draft posts.

Prompt

Suggest a five-post social calendar from this research. After I approve the plan, create the drafts in Creagency.

Expected outcome

The agent separates planning from draft creation.

Competitive summary

Turn a competitor note into a careful brand-safe post.

Prompt

Create one LinkedIn draft from this competitive summary. Avoid naming competitors unless the source text already does.

Expected outcome

A brand-safe draft is created without overclaiming.

Asset-backed insight

Attach a chart or image to a research post.

Prompt

Upload ./chart.png and create one LinkedIn draft explaining the main insight in plain language.

Expected outcome

The image is attached and the post stays in draft.

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

Perplexity 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

Perplexity MCP server docsOpen

Creagency Agent READMEOpen

Creagency skill docsOpen