All clients
Other clients
The Creatorland Data MCP speaks the standard MCP HTTP transport with OAuth 2.1, any client that supports custom remote MCP servers can connect.
Setup
Other clients
Loading setup…
- Who it’s for
- Anyone using an MCP-capable client not on the explicit list above.
- Compatibility
- The server is available at `https://mcp.creatorland.com/mcp` over HTTPS only. It publishes OAuth 2.1 discovery on its branded issuer host `https://data-mcp.creatorland.com` — protected-resource metadata at `/.well-known/oauth-protected-resource` (RFC 9728) and authorization-server metadata at `/.well-known/oauth-authorization-server` (RFC 8414) — and supports Dynamic Client Registration (RFC 7591) at `/oauth/register`, so a spec-compliant client can register and authenticate automatically with no manual allowlisting. If your client supports custom MCP servers via a URL field, you have what you need.
- Verify the connection
- After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.
Troubleshooting
- Discovery from a bare 401: an unauthenticated request to `/mcp` returns `WWW-Authenticate` pointing at `/.well-known/oauth-protected-resource`; from there a client finds the authorization server (issuer `https://data-mcp.creatorland.com`) and the `registration_endpoint`.
- The default scope is `mcp`. For clients that require a manual scope list, request `mcp`; the server returns the scopes your customer is provisioned for.
- If you’re building or evaluating a new MCP client, it connects self-serve through the discovery flow above, no allowlisting needed, and you can [talk to us](/request-access) if you want a dedicated setup page.
