# SurrealDB Cloud MCP

> The Model Context Protocol server for SurrealDB Cloud. It exposes SurrealDB Cloud - organisations, instances, billing, and Agent memory contexts - to MCP clients and agents as tools, over a single streamable HTTP endpoint.

This host serves that one MCP server and nothing else: no REST API, no documentation site, no other endpoints. The platform API lives on https://api.surrealdb.com, which mounts the same MCP server at `/api/mcp`. A token minted on either origin is accepted by both.

## Endpoint

- [MCP endpoint](https://mcp.surrealdb.com): Streamable HTTP transport. Add this URL to an MCP client, or POST JSON-RPC to it directly.

## Discovery

- [Protected resource metadata](https://mcp.surrealdb.com/.well-known/oauth-protected-resource): RFC 9728. Names this resource and the authorization server that protects it.
- [Authorization server metadata](https://mcp.surrealdb.com/.well-known/oauth-authorization-server): RFC 8414. The authorize, token, and client registration endpoints.

## Authentication

Authorization is OAuth 2.1 with PKCE (S256) and RFC 7591 dynamic client registration, so a client registers itself and no credential has to be issued by hand. Start at the protected resource metadata above, then register, authorize, and exchange the code for a token; send the result as `Authorization: Bearer <token>` on every request. Most MCP clients drive the whole flow once the endpoint URL is added.

- [Dynamic client registration](https://mcp.surrealdb.com/oauth/register): RFC 7591 registration endpoint
- [Agent authentication guide](https://surrealdb.com/auth.md): How agents obtain and use SurrealDB credentials

## Documentation

- [SurrealDB Cloud](https://surrealdb.com/cloud): The managed service this server controls
- [SurrealDB documentation](https://surrealdb.com/docs): Product, SurrealQL, and API reference
- [Platform API](https://api.surrealdb.com/llms.txt): The REST API on https://api.surrealdb.com, which also serves this MCP server under `/api/mcp`