For agentic IDE workflows
Social media scheduling for 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.
Antigravity uses a shared MCP config path, and Creagency supplies a local stdio server for bounded social tools.
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.Scoped API key
Draft first
Confirmed publish
Quick start
Get Antigravity working with Creagency.
Move from completed work to scheduled posts inside an agentic IDE.
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 Antigravity 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 Antigravity 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 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.
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.
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"
}
}
}
}Examples
Antigravity prompts you can actually use.
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
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.
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.
FAQ
What Antigravity 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 Google Antigravity with Creagency.
Install the skill, connect the CLI or local MCP server, and start with one draft that your team can review.