For the complete documentation index, see llms.txt. This page is also available as Markdown.

Authentication and authorization

See how Data Product MCP enforces DataOS identity, access, and policy controls.

MCP defines how clients and servers exchange messages. Authentication and authorization are enforced by the MCP server implementation and the transport configuration used to reach it.

How Data Product MCP enforces access

Every request is evaluated using the caller's DataOS identity.

If a user cannot access a Data Product, table, column, or value in DataOS, the assistant cannot access it through Data Product MCP. If a value is masked for the user in DataOS, the assistant receives the masked value.

This keeps the assistant inside the same governance boundary as every other DataOS interface.

How clients authenticate

Data Product MCP accepts two authentication methods, each on its own endpoint:

Method
Endpoint
How the client authenticates

OAuth

https://<instance-url>/mcp/api/v1

The user signs in with their DataOS account in a browser. No token is needed.

API token

https://<instance-url>/dataproduct-mcp/api/v1

The client sends a DataOS API token in the apikey header.

With OAuth, an unauthenticated request returns 401 with a WWW-Authenticate header that points to the protected resource metadata at https://<instance-url>/mcp/api/v1/.well-known/oauth-protected-resource. Clients that follow the MCP authorization flow use it to find the authorization server and sign the user in. For clients that need the OAuth settings entered manually, see Custom client.

Both methods run each request as the signed-in user or the token owner.

What the server does on each request

Data Product MCP:

  1. Authenticates the caller.

  2. Authorizes the requested operation.

  3. Applies Data Product policies.

  4. Returns only the response the caller is allowed to receive.

The host can improve the conversation around the answer. It does not expand the user's access.

Last updated

Was this helpful?