AI Agent Ready
Every command outputs structured JSON. Designed for LLMs and automation pipelines to parse, plan, and execute social media workflows.
Pixalera for AI agents
AI agent social media posting means an AI agent such as Claude Code, ChatGPT, Cursor, or OpenClaw drafts, schedules, and publishes posts for you. Pixalera is the agentic social media scheduling platform that makes this work: it exposes an MCP server and a CLI, so any agent can post to 8+ platforms while you approve the plan.
Please make sure there is always a human in the loop. Last updated: October 2026
Every agent below has a dedicated Pixalera guide. Each row shows how that agent connects and how it authenticates; open the guide for install steps, example prompts, and setup details.
| Agent | Made by | How it connects to Pixalera | Authentication | Guide |
|---|---|---|---|---|
| OpenAI | Custom MCP connector in ChatGPT | Private key in the MCP URL | ChatGPT guide | |
| Anthropic | Custom MCP connector in Claude | Private key in the MCP URL | Claude guide | |
| Anthropic | claude mcp add, or the Pixalera CLI | PIXALERA_API_KEY (CLI) or key in URL (MCP) | Claude Code guide | |
| OpenAI | Pixalera CLI with a SKILL.md in your project | PIXALERA_API_KEY | Codex guide | |
| Microsoft | MCP server entry in mcp.json | Private key in the MCP URL | VS Code guide | |
| Cursor | MCP server entry, or the Pixalera CLI | PIXALERA_API_KEY (CLI) or key in URL (MCP) | Cursor guide | |
| Gemini CLI extension settings, or connected app | Private key in the MCP URL | Gemini guide | ||
| Open source | Pixalera skill via the skills CLI | PIXALERA_API_KEY | OpenClaw guide | |
| Nous Research | Pixalera skill (npx skills add) | PIXALERA_API_KEY | Hermes Agent guide | |
| xAI | Plugin command with the Pixalera MCP URL | PIXALERA_API_KEY stored as a bot secret | Grok Bot guide | |
| xAI | MCP server entry in workspace settings | Private key in the MCP URL | Grok Build guide | |
| DeepSeek | MCP server entry in the client config | Private key in the MCP URL | DeepSeek guide | |
| Moonshot AI | MCP link in Kimi Code, or the Pixalera CLI | PIXALERA_API_KEY (CLI) or key in URL (MCP) | Kimi K3 guide | |
| Meta | MCP link pasted into a setup prompt | Private key in the MCP URL | Muse guide | |
| Manus | Custom connector in Settings → Connectors | PIXALERA_API_KEY as a Bearer header | Manus guide | |
| Manus | Pixalera connector in Cue's connectors | PIXALERA_API_KEY as a Bearer header | Cue guide | |
| Perplexity | Pixalera skill (npx skills add) | PIXALERA_API_KEY | Perplexity Computer guide | |
| Qwibit AI | Pixalera skill (npx skills add) | PIXALERA_API_KEY | nanoclaw guide | |
| Open source | Pixalera skill (npx skills add) | PIXALERA_API_KEY | Paperclip guide | |
| Any MCP client | Any MCP-compatible client, pointed at the Pixalera MCP URL | Private key in the MCP URL | MCP Server guide | |
| Pixalera | The Pixalera CLI itself — any agent that runs shell commands | PIXALERA_API_KEY | AI Agents CLI guide |
Using an MCP client that is not listed? Any MCP-compatible tool can use the Pixalera MCP server. Any agent that runs shell commands can use the Pixalera CLI.
AI agents connect to Pixalera through one of three surfaces: the hosted MCP server, the Pixalera CLI, or a connector inside the agent's own settings. All three reach the same Pixalera account and the same channels.
| Surface | Used by | Authentication | Media and tools |
|---|---|---|---|
| Pixalera MCP server | ChatGPT, Claude, Cursor, VS Code, Gemini, Kimi Code, DeepSeek, Muse, Manus, Cue, Grok Build | Your private key in the MCP URL; Manus and Cue send it as a Bearer header | Full toolset: posting, scheduling, ideas, analytics and product lookups |
| Pixalera CLI | Claude Code, Codex, OpenClaw, Hermes Agent, nanoclaw, Paperclip, Perplexity Computer, Grok Bot | PIXALERA_API_KEY from your Pixalera settings | Upload images, videos and documents from disk; every command returns JSON |
| In-app connectors | ChatGPT connectors, Claude connectors, Manus and Cue connectors, Cursor MCP settings, Gemini CLI extensions | One-time setup with your private key; plugins bundle the CLI or MCP server | Same tools as the MCP server, configured inside the agent's own UI |
Connecting takes three steps and about two minutes: choose the MCP link or the CLI, set your key, then ask the agent to post. Each agent guide repeats these steps with the exact commands for that tool.
MCP clients (Claude, ChatGPT, Cursor, VS Code, Gemini, Kimi Code, Grok Build) take the hosted Pixalera MCP link. Agents that run shell commands (Claude Code, Codex, OpenClaw, Hermes Agent, nanoclaw, Paperclip, Perplexity Computer) take the Pixalera CLI.
# Option A: MCP link (paste into your MCP client)
https://api.pixalera.in/mcp/YOUR_API_KEY
# Option B: Pixalera CLI (any agent that runs commands)
npx pixalera-cli initThe MCP link carries your private key, so the agent only reaches the workspace that created it. The CLI reads PIXALERA_API_KEY from your environment; copy the key from your Pixalera settings.
# MCP: your private key is already in the URL
# CLI: export the key once
export PIXALERA_API_KEY=your_api_key
# Verify the agent can see your channels
pixalera channels:listDescribe the post in plain language. The agent lists your channels, uploads media, applies platform settings, and schedules the post. Review the plan before it publishes.
You: Schedule a LinkedIn post and an X thread about the launch for tomorrow at 9am, attach ./assets/launch.png
Agent: Scheduled 2 posts for 09:00
- LinkedIn: 1 post with image
- X: 3-part thread with image
Want me to add Instagram too?Connect your accounts in Pixalera once. From then on any AI agent can post to any of them through the MCP server or the CLI, and Pixalera publishes at the time you set.








An agent connected to Pixalera can list your channels, upload media, create scheduled posts and threads, apply platform-specific settings, and read analytics. Every response is structured, so the agent can plan the next step on its own.
Every command outputs structured JSON. Designed for LLMs and automation pipelines to parse, plan, and execute social media workflows.
Post to Instagram, Facebook, Threads, YouTube, X, LinkedIn, Pinterest and Bluesky from a single CLI.
Create multi-part posts and refined captions, each with their own media, converted to platform-native formats.
Upload and attach images, videos and documents. Supports PNG, JPG, MP4, MOV, PDF and many more formats.
Schedule posts with precise timestamps, create drafts for review, and batch schedule entire content campaigns.
Dynamic discovery of platform features like boards, playlists and audience settings per connected channel.
The Pixalera CLI is the tool behind the skill. Install it once, set PIXALERA_API_KEY, and an agent can discover your channels, create posts, and read analytics with plain commands that return JSON.
# Install the CLI
npx pixalera-cli init
# Set your API key
export PIXALERA_API_KEY=your_api_key
# List your connected platforms
pixalera channels:list
# Create your first post
pixalera posts:create \
-c "Hello from Pixalera!" \
-s "2026-11-01T12:00:00Z" \
-i "your-channel-id"List all your connected social media accounts and discover platform-specific features like boards and playlists.
pixalera channels:list
# Get platform settings
pixalera channels:settings <id>Compose posts with content, media and platform-specific settings. Use simple flags for quick posts or JSON files for complex campaigns.
pixalera posts:create \
-c "Check out our new feature!" \
-m "screenshot.png" \
-s "2026-11-15T09:00:00Z" \
-i "x-id,linkedin-id"
# Complex post from JSON
pixalera posts:create --json campaign.jsonList scheduled posts, read channel and post analytics, and upload media for reuse across campaigns.
# List scheduled posts
pixalera posts:list
# Get channel analytics (last 30 days)
pixalera analytics:channel <id> -d 30
# Get analytics for a specific post
pixalera analytics:post <post-id> -d 7
# Upload media for reuse
pixalera upload video.mp4Post to multiple platforms simultaneously, each with their own media and platform-specific settings.
# Post to multiple platforms at once
pixalera posts:create \
-c "Launching our new feature today!" \
-m "banner.png" \
-s "2026-11-01T09:00:00Z" \
-i "x-id,linkedin-id,facebook-id"
# Post with platform-specific settings
pixalera posts:create \
-c "check out this tutorial" \
-m "video.mp4" \
-s "2026-11-01T09:00:00Z" \
--settings '{"pinterest":[{"board":"Tutorials"}]}' \
-i "pinterest-id"
# Batch schedule a week of content
for day in 1 2 3 4 5; do
pixalera posts:create \
-c "Day $day content" \
-s "2026-11-0${day}T09:00:00Z" \
-i "x-id,linkedin-id"
doneYes. Agents with recurring jobs can run Pixalera headless: OpenClaw has cron automations, nanoclaw has built-in scheduled jobs, and any always-on agent can run the CLI on a routine. Keep a human approval step for publishing.
Agents like OpenClaw and nanoclaw run as a persistent daemon and take messages from chat apps. Send one message and the agent discovers your accounts via Pixalera, uploads media, and schedules the posts while you go about your day.
You: Post my blog article to X, LinkedIn, and Instagram with the cover image, schedule for tomorrow at 9am
Agent: Done! Posts scheduled:
- X: scheduled 9:00 AM
- LinkedIn: scheduled 9:00 AM
- Instagram: scheduled 9:00 AM
Post ID: abc-123OpenClaw supports cron automations. Set up a recurring job that checks for new content and posts it to all your platforms automatically, with no manual trigger needed.
{
"heartbeat": [
{
"cron": "0 9 * * 1-5",
"prompt": "Check ~/content/pending for new posts. Upload any media, then schedule to X, LinkedIn, and Instagram for today at noon. Move posted files to ~/content/done."
}
]
}---
name: pixalera
description: Social media automation CLI for
scheduling posts across 8+ platforms
metadata:
openclaw:
requirements:
env:
- PIXALERA_API_KEY
binaries:
- pixalera
---
# Available Commands
- pixalera channels:list
- pixalera channels:settings <id>
- pixalera posts:create
- pixalera upload <file>
- pixalera analytics:channel <id>Every command shares your account's existing permissions. Read-only checks are safe to run freely; review content and publishing actions before approving them.
| Command | Description |
|---|---|
pixalera channels:list | List all connected social media accounts |
pixalera channels:settings <id> | Get platform-specific settings schema |
pixalera posts:create | Create and schedule a new post |
pixalera posts:list | List all scheduled and published posts |
pixalera posts:delete <id> | Delete a scheduled post |
pixalera ideas:list | Read the ideas board |
pixalera ideas:create | Save a new content idea |
pixalera analytics:channel <id> | Get analytics for a channel |
pixalera analytics:post <id> | Get analytics for a specific post |
pixalera upload <file> | Upload media and get a reusable URL |
Pixalera connects your social channels, and every agent guide works with the accounts below. For an agent-specific walkthrough, open any guide from the table above.
| Platform | Description |
|---|---|
| Feed posts, stories, and reels | |
| Text posts, links, and media | |
| Threads | Text posts and reply threads |
| YouTube | Video uploads, titles, and tags |
| X (Twitter) | Tweets, threads, and reply controls |
| Professional posts and image carousels | |
| Pins, boards, and link pins | |
| Bluesky | Posts, replies, and media |
It is when an AI agent, rather than a person clicking through a dashboard, drafts, schedules, and publishes posts on your connected accounts. With Pixalera the agent calls the MCP server or the CLI, picks the right channels, applies platform settings, and schedules the post while you review the plan.
Any agent that can call MCP tools or run shell commands: ChatGPT, Claude, Claude Code, Codex, Cursor, VS Code, Gemini, Grok, DeepSeek, Kimi, Manus, OpenClaw, Hermes Agent, Paperclip and more. The table above lists every dedicated guide.
Yes. Create a private key in Pixalera Settings → Developers. The MCP URL carries the key, and the CLI reads it from the PIXALERA_API_KEY environment variable. Treat the key like a password.
The MCP server is a hosted connection that MCP-compatible clients (ChatGPT, Claude, Cursor, Gemini) call directly. The CLI is a local tool for agents that run shell commands (Claude Code, Codex, OpenClaw, Paperclip). Both reach the same workspace and the same channels.
Yes. Agents with recurring jobs can run Pixalera headless: OpenClaw has cron automations, nanoclaw has built-in scheduled jobs, and any agent on a server can run the CLI from a cron task. Keep a human approval step for publishing.
Pixalera MCP and CLI access requires an active Pro plan. Your normal workspace permissions, credits and limits still apply to every action the agent takes.
Instagram, Facebook, Threads, YouTube, X (Twitter), LinkedIn, Pinterest and Bluesky — the same accounts you connected in your Pixalera workspace. Available actions can differ by platform and account permissions.
Revoke the key in Pixalera Settings → Developers and remove the connection from the agent. Never paste the full MCP URL into public chats, screenshots or source code.
Want the protocol details? Read the Pixalera MCP server guide. Last updated: October 2026.
Connect your AI agent to Pixalera and let it handle social media posting across all your platforms.