Other MCP clients · Serenity

All documentation

Serenity connects through standard MCP OAuth. Add the server URL, and your agent opens a browser tab where you sign in, choose one project memory, and approve read-only or read-and-write access. No token is copied by hand. A private bearer token from Your project memories remains available as a fallback for environments without a browser.

Connection settings

Transport: Streamable HTTP
Server URL: https://serenity.sire.run/mcp
Authorization: OAuth 2.1 with PKCE, discovered from the server; dynamic client registration; scopes memory:read and memory:write
Discovery: /.well-known/oauth-protected-resource/mcp and /.well-known/oauth-authorization-server
Fallback: Authorization: Bearer YOUR_TOKEN

A client that follows the MCP authorization specification needs only the server URL. An unauthenticated request receives a challenge that points to the resource metadata; the client registers itself, opens the browser for consent, and exchanges the code with PKCE. Loopback redirect URIs are accepted for desktop and CLI agents.

Client names shown on the consent page are supplied by the connecting app and are not verified. Every grant is limited to one brain and to the access you approve.

Bearer token fallback

For a client that cannot run the browser flow, create a token in Your project memories and send it as a bearer header. For an application you build, use an MCP SDK’s Streamable HTTP client and load the token from your backend secret store. Keep credentials on your application’s server; direct browser JavaScript requests are not supported. Follow MCP initialization and session handling; this is not a REST memory API. Clients that only support local stdio need a compatible adapter, which this hosted guide does not qualify.

Manage the connection

Connections appear under Connected agents, where you can disconnect any agent. Access tokens are short-lived and renewed automatically; each renewal rotates the refresh token, so a captured old token stops working. A connection expires after 30 days and your agent simply asks you to connect again.

Try your first memory

Restart or reconnect your harness, then ask: “Use Serenity to remember that this project’s test word is amber heron.” Next ask: “Use Serenity to recall this project’s test word.” Check the tool results. A successful connection alone does not verify a saved memory.

Serenity does not automatically ingest your repository or chat history. Your agent must use its memory tools. Writes use the configured embedding provider.