AI Agents (MCP)
PostClaw runs a remote Model Context Protocol server. Connect an AI assistant to it and you can ask, in plain words, “write three posts for next week and schedule them on my Facebook Page”. The assistant checks your channels, drafts the posts and puts them on your calendar, as you.
Available on every plan, including Free. Your plan’s limits apply exactly as they do in the app.
What you need
- A PostClaw account with at least one connected channel.
- An MCP client that can send an
Authorizationheader over Streamable HTTP: Claude Code, Cursor, VS Code, and most other MCP clients. - A token from Settings → AI agents.
Claude.ai and ChatGPT in the browser are not supported yet. They need an OAuth sign-in, which is planned.
Connect in two minutes
- Open Settings → AI agents and click New token.
- Give it a name you will recognise (for example “Cursor on my laptop”) and choose its permissions.
- Copy the token. It is shown only once. If you lose it, revoke it and create a new one.
- Add the server to your client. The settings page shows these snippets with your token already filled in.
Server URL: https://app.postclaw.fun/mcp
Claude Code
claude mcp add --transport http postclaw https://app.postclaw.fun/mcp --header "Authorization: Bearer YOUR_TOKEN"
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"postclaw": {
"url": "https://app.postclaw.fun/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
VS Code (.vscode/mcp.json)
{
"servers": {
"postclaw": {
"type": "http",
"url": "https://app.postclaw.fun/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
Then ask your assistant something like “Which channels do I have in PostClaw?” to check the connection.
Permissions
Each token has its own permissions. The assistant only sees the tools its token allows.
| Permission | What the assistant can do |
|---|---|
| Read (always on) | See channels, posts, media and analytics, and get posting-time suggestions |
| Write | Create and edit drafts, upload media, write posts with AI, create AI images |
| Publish (off by default) | Schedule, publish, unschedule and delete posts on your real accounts |
Without Publish, an assistant can only leave drafts for you to review and approve in PostClaw. Turn it on only for assistants you trust to post on your behalf.
You can keep up to 10 active tokens. Revoking a token takes effect on the assistant’s next request.
Tools
| Tool | Permission | What it does |
|---|---|---|
list_channels | Read | Connected accounts and pages you can publish to |
list_posts, get_post | Read | Drafts, scheduled and published posts, with live URLs and errors |
get_analytics | Read | Totals, per-platform breakdown, best times, top posts |
suggest_posting_times | Read | Good time slots per platform |
list_media | Read | Recently uploaded media |
generate_post | Write | Post text from a brief, optionally in your brand voice |
adapt_post | Write | One piece of content rewritten for each platform |
create_image | Write | AI images for your posts |
upload_media, add_media_to_post | Write | Attach your own images and video |
create_post, update_post | Write | Create and edit drafts; setting a time schedules the post (needs Publish) |
publish_post | Publish | Publish now and return each platform’s live post URL |
unschedule_post | Publish | Move a scheduled post back to draft |
delete_post | Publish | Remove a post from PostClaw |
Media must be an https:// URL or a file sent through upload_media.
create_post and publish_post accept an optional idempotency_key. If the assistant retries a call with the same key within 24 hours, PostClaw returns the first result instead of creating or publishing twice.
Limits and credits
An assistant works under the same plan as you do in the app:
- Posts per month, AI credits and image quota count the same whether you work in PostClaw or through an assistant.
- AI tools use your own AI key when you have one connected in Settings.
- Each token can make up to 60 requests per minute.
- Every call is logged to your account.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
401 / “invalid token” | The token is wrong or was revoked | Create a new token and update your client |
429 | More than 60 requests a minute from one token | Wait a few seconds; the response says how long |
| A tool is missing | The token lacks the permission for it | Create a token with that permission |
scope_missing | Scheduling or publishing without the Publish permission | Enable Publish on a new token, or schedule from the app |
quota_exceeded, credit_cap_exceeded | Your plan’s monthly limit is used up | Wait for the next period or upgrade |
| ”your … configuration failed” | Your own AI key returned an error (quota, billing, expired sign-in) | Fix or remove the key in Settings → Providers |
Keep your tokens safe
A token acts as you. Treat it like a password:
- Do not commit it to a repository or paste it into shared chats.
- Use one token per device or tool, so you can revoke one without breaking the others.
- Revoke tokens you no longer use in Settings → AI agents.