Agent setup

Set up Creagency with Google Antigravity

Add Creagency as local tooling for Antigravity so the agent can turn workspace context into drafts without taking direct control of your channels.

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

Antigravity 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

Verified feature announcement

After Antigravity validates a feature, it drafts the announcement in Creagency.

Prompt

Use Creagency to create a LinkedIn draft for the feature you just verified. Include the user benefit and do not publish.

Expected outcome

A LinkedIn draft is ready for marketing review.

Bug fix release note

Turn a tested fix into a short customer-facing post.

Prompt

Draft one X post about this fix. Mention what changed, not implementation details. Leave it as a Creagency draft.

Expected outcome

A concise X draft is created with no private implementation details.

Campaign from workspace context

Use workspace context to create several draft posts.

Prompt

Create three Creagency drafts for this launch: one LinkedIn, one X, and one Threads. List accounts first.

Expected outcome

Three platform-specific drafts are created after account discovery.

Schedule after review

Schedule only after a human approves the copy.

Prompt

Show me the three draft summaries. If I approve, schedule them for next week at 9am local time.

Expected outcome

The agent waits for approval before scheduling.

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

Antigravity 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

Google Antigravity MCP codelabOpen

Creagency Agent READMEOpen

Creagency skill docsOpen