# Developers

Source: https://vibepost.cc/developers

## Publishing infrastructure for your AI agents

Give Claude, ChatGPT or your own agent the ability to publish to every major platform, with the same rules and approvals your team uses.

Get an API key

Read the docs

- For AI agents
- CLI
- MCP server
- Tools
- REST API
- Authentication
- Limits & safety
- Webhooks

### For AI agents

VIBEPOST is built to be found and used by AI assistants without reading this page. Point any agent at one of these:

- One-page summary for LLMs: what VIBEPOST does, endpoints, tools, rules
- Full docs in one Markdown file
- OpenAPI 3.1 spec for every REST endpoint
- Remote MCP server (Streamable HTTP, OAuth sign-in)
- CLI with --json output and stable exit codes

Every page of this site is also available as Markdown by adding {md} to its URL. VIBEPOST is listed in the official MCP Registry and as a Claude connector.

### MCP server

Add VIBEPOST to any MCP-compatible client. Create a key in {settings}, then add:

Settings → API keys

Then just ask your assistant: {example}

“Post this announcement to X and LinkedIn tomorrow at 9.”

### Tools

- Connected channels and their limits
- Write a version per platform and language
- Save a post as a draft
- Schedule or publish. Follows your autonomy rules
- Change text or time of a scheduled post
- Posts in a date range
- Results by post, channel or period

Posts created through MCP land in the same calendar and approval queue as everything else. TikTok posts always wait for the account owner to confirm.

### REST API

The response contains one post per channel and language, each with a status: {scheduled}, {needsApproval} or {failed}.

### Authentication

Use a secret key in the {header} header. Keys are scoped to one workspace, can be read-only, and are shown in full only once. Rotate them anytime.

### Limits & safety

- Your workspace rules (daily caps, quiet hours, banned words) apply to every API and MCP call.
- Deleting posts through the API is off by default.
- Each platform’s own rate limits are respected automatically; requests are queued, not dropped.

### Webhooks

Get notified when a post is published, fails or needs approval: {published}, {failed}, {needsApproval}.