Authentication
Beeper Desktop API requires an access token for all endpoints.
Create a token
Section titled “Create a token”- Make sure Beeper Desktop API is enabled and running
- Open Settings → Developers in Beeper Desktop
- Click the ”+” button next to “Approved connections”
- Follow the instructions to create your token
If you want to allow your users to interactively allow your application to access their Beeper Desktop, you can use OAuth 2.0 with PKCE for authentication
RFC 8414 compliant metadata is available at http://localhost:23373/.well-known/oauth-authorization-server
Built-in MCP server uses oAuth natively for authentication. See authorization page of the MCP specification for more details.
Get in touch with us for help, questions or feedback.
Use your token
Section titled “Use your token”All requests to Beeper Desktop API, including requests to the MCP endpoints (/v0/mcp, /v0/sse), support the Authorization header with the Bearer token for authentication.
When used with the MCP server, MCP authentication is bypassed and the token is used directly.
Authorization: Bearer <your_token>