Skip to main content
PostlyBee provides a Model Context Protocol server for AI clients that can inspect connected accounts and posts, validate platform requirements, schedule content, update provider settings, and generate media.

​
Endpoint

The modern endpoint uses stateless Streamable HTTP. Compatible clients can discover PostlyBee’s OAuth 2.1 metadata automatically and request mcp:read and mcp:write scopes.

​
Authentication options

OAuth connection

Recommended for clients that support protected-resource discovery, dynamic client registration, and PKCE S256.

Workspace API key

Use Authorization: Bearer YOUR_API_KEY in clients that accept a static header configuration.
OAuth access tokens and workspace REST API keys are separate credentials. Both use the Bearer header at the MCP endpoint.

​
Available capabilities

The modern MCP server exposes tools for:
  • Listing connected social accounts and validating provider schemas.
  • Listing posts within a UTC date range.
  • Scheduling posts after user confirmation.
  • Updating provider-specific settings for drafts and queued posts.
  • Discovering video options and running helper functions.
  • Generating images and videos.
Write tools require the mcp:write scope. Read-only inspection tools require mcp:read. Post deletion is not available through MCP.

​
Legacy endpoint

The older API-key SSE endpoint remains available for existing clients:
New integrations should use the Streamable HTTP endpoint instead because it supports modern MCP discovery and OAuth.
Last modified on August 26, 2026