Skip to main content
Datacircle’s MCP server is https://api.datacircle.dev/mcp (Streamable HTTP). Add it to your client, sign in with your Datacircle email, and your agent calls the API for you: every call costs what the same REST call costs (Pricing), from the same balance.

​
Add it

Signing in opens datacircle.dev: sign in with your email code (a new account gets the sign-up credit), check which app asks and where it sends you back, then Allow. The app gets an access token that works on /mcp only. A client that sends headers can skip OAuth and use your API key:
To cut every connected app off, reset your API key: their access tokens stop working with it.

​
Tools

Each tool makes one REST call with your key and answers that call’s JSON (isError: true when its status is 400 or more).

​
For developers

  • No session and no stream: every POST /mcp gets one JSON answer, and GET /mcp is 405. Protocol versions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05.
  • Each tool declares an outputSchema, its REST call’s 200 answer as the API reference documents it, and the hints readOnlyHint, destructiveHint, idempotentHint and openWorldHint. The answer comes as structuredContent and as text. A failed call (isError: true) answers its error JSON as text only.
  • get_linkedin_profile’s outputSchema lists each provider’s top-level fields only, so it stays small in an agent’s prompt. The API reference has the nested fields.
  • No token, or a bad one: 401 with WWW-Authenticate: Bearer resource_metadata="https://api.datacircle.dev/.well-known/oauth-protected-resource/mcp".
  • OAuth 2.1: /.well-known/oauth-authorization-server lists the endpoints. Dynamic client registration at POST /oauth/register, the authorization code with PKCE (S256 only), public clients, or a client secret if you register with one. Or skip registration: send your client ID metadata document’s https URL as your client_id. The document must list that same client_id and your redirect_uris. Keep it under 5 KB and serve it without a redirect.