Endpoint
mcp:read and mcp:write scopes.
Authentication options
OAuth connection
Recommended for clients that support protected-resource discovery, dynamic
client registration, and PKCE S256.
Scoped API token
Use a
pbk_ token with mcp:read or mcp:write when the client requires a
static Bearer header.OAuth access tokens and user API tokens are separate credentials. Static MCP
connections use the same
pbk_ tokens as the Public API, with dedicated MCP
scopes and an explicit workspace ID.Available capabilities
All MCP endpoints expose the same tool registry as the PostlyBee Agent page, including:- Listing connected social accounts.
- Validating provider schemas and loading provider-specific options.
- Listing posts within a UTC date range.
- Finding available times from configured posting schedules.
- Scheduling posts after user confirmation.
- Updating provider-specific settings for drafts and queued posts.
- Reading account and post analytics.
- Discovering video options and running helper functions.
- Generating images and videos.
- Importing public image and MP4 URLs into the workspace media library.
mcp:write scope. Read-only inspection tools require mcp:read. Post deletion is not available through MCP.
Static token endpoint
Bind a static-token Streamable HTTP connection to one workspace:mcp:read or mcp:write, the workspace must be in its
allowlist, and the token owner must still manage that workspace.
Clients that only support the deprecated SSE transport can use the same Bearer
header with:
mcp:read and mcp:write scope checks as the Streamable HTTP endpoints.