About
Features
Your agent can do nearly everything you can.
An agent can receive deliveries, like any other endpoint.
Terms
An endpoint for one receiving AI conversation or automation.
A URL that receives signed JSON deliveries.
The verified connection behind an agent endpoint.
Guides
The Curation Space MCP server lets an agent such as Claude Code, Codex, or OpenCode work in Curation Space as you.
A Webhook endpoint sends each delivery as a signed JSON POST to one URL.
Connect your agent
The Curation Space MCP server lets an agent such as Claude Code, Codex, or OpenCode work in Curation Space as you. It can manage your curations and their links, search your Library and public work, update your profile and images, connect feeds and sitemaps, and set up delivery.
How do I connect my agent?
Copy this prompt into your agent harness, such as Claude Code, Codex, or OpenCode. It gives your agent what it needs to add the server to its own configuration.
Add the Curation Space MCP server to your MCP configuration. Add it at the user level, so it is available in every project, unless I ask otherwise. Server details: - Name: curationspace - URL: https://mcp.curation.space/mcp - Transport: Streamable HTTP. It is a remote server: there is no local command to run and no SSE endpoint. - MCP protocol revision: 2026-07-28 only. Earlier revisions are rejected. If your configuration lets you choose or pin a protocol revision, set it to 2026-07-28. In Codex, turn on the mcp_2026_07_28 feature: without it, Codex uses an earlier revision. - Authentication: OAuth 2.1 authorization code flow with PKCE. An unauthenticated request returns a WWW-Authenticate challenge pointing to the protected resource metadata at https://mcp.curation.space/.well-known/oauth-protected-resource/mcp. The authorization server is https://auth.curation.space. - Scopes: mcp:connect (required) and offline_access (lets you refresh access without another sign-in). - Client registration: Client ID Metadata Document (CIMD). Dynamic client registration is not available. If your configuration lets you choose a registration strategy, choose CIMD. - Do not add an API key, bearer token, or Authorization header. The server accepts only OAuth access tokens issued for it; Curation Space API keys and website sessions do not work. After you save the configuration: 1. Tell me exactly what I need to do to finish connecting, such as restarting you or running a login command. Start the OAuth sign-in yourself if you can. I will sign in to Curation Space and approve access in my browser. 2. Once connected, call list_my_curations to confirm that the connection works.
Codex connects only with its mcp_2026_07_28 feature turned on. Without it, Codex fails with the error "MCP-Protocol-Version header is required." Turn it on in ~/.codex/config.toml before you connect:
[features] mcp_2026_07_28 = true
What can my agent do?
Whatever its tools allow, acting as you. Notifications remain app-only. Agents do not delete accounts, change sign-in access, or complete human verification. Every tool reads and changes only what your account can access; no tool accepts a user ID.