Use the OAuth MCP endpoint whenever the client supports protected-resource discovery. For clients that require a static header, create a pbk_ API token with MCP scopes and use the workspace-specific endpoint.
Claude Code
After adding the server, ask Claude to list the available PostlyBee accounts before scheduling content.
Generic configuration
Clients that accept JSON server configuration typically use a structure similar to:
Configuration keys vary by client. Select Streamable HTTP or HTTP transport, not the deprecated SSE transport.
OAuth discovery
Clients supporting OAuth can start with only the MCP URL. PostlyBee advertises protected-resource and authorization-server metadata under /.well-known, supports dynamic client registration, and requires PKCE S256 for authorization-code exchange.
During authorization, sign in to PostlyBee, choose the intended workspace, review the requested scopes, and approve the connection.
Verify the connection
Ask the client to perform a read-only action first:
List all PostlyBee social accounts available in this workspace.
Then test a publishing workflow without immediately sending content:
Validate the requirements for my selected account and prepare a draft post. Ask for confirmation before scheduling it.
Troubleshooting
Last modified on August 26, 2026
