Skip to content
Data MCP Directory

GUIDE, read 10 Nov 2026

Whether an agent sees what the asking person may see depends on whether the server runs calls as that person or as one shared credential

The directoryAll guides

OAuth on behalf of the user ties each call to a person

When a server completes OAuth for the person at the keyboard, the vendor can apply that person's permissions to every tool call. Per the docs for the Atlan MCP server, OAuth makes each tool call run as the signed-in user, so tools run with their own permissions and actions are attributed to them. Per the docs for the Cube MCP server, every tool runs as the authenticated user, and queries respect Cube permissions including row-level security.

Per Omni's docs, MCP tools run with the permissions of a specific Omni user, so results include only what that user can access. Per Sigma's help page, the server inherits the user's Sigma account permissions, and access needs the 'Use Sigma MCP with OAuth' account-type permission plus at least Can view on documents or Can use on connections. Per Tableau's README, the hosted server uses OAuth 2.1 so each user signs in as themselves and per-user Tableau permissions are enforced.

Google documents OAuth 2.0 with IAM for the BigQuery remote server, so access follows the authenticated Google Cloud identity. Per Databricks, the dbsql MCP runs SQL using the caller's Unity Catalog and warehouse permissions, so results are scoped to the asking user.

Service accounts and shared keys scope the agent, not the person

A shared credential gives every asker the same view. Per the README of the Fivetran MCP Server, the server uses one Fivetran API key and secret, so agent actions run with that credential's scope instead of the asking user's identity, and OAuth resource-server support in streamable-http mode is not yet functional. Secoda's docs say the open-source wrapper authenticates with a single API_TOKEN, one shared token per server process, while the Secoda-hosted endpoint verifies the user's workspace and AI permissions.

Select Star's page describes an API token sent as a Bearer header. No per-user OAuth is described, and the page does not say results are limited to the asking user's permissions (none found on 10 Nov 2026). Per Collibra's README, stdio mode uses one server-wide credential, while HTTP mode advises that MCP clients supply their own Basic Auth headers per request.

Alation's guide describes the service-account route: the agent gets the data and features allowed by the role assigned to the service account. Per OpenMetadata's docs, unattended agents should use a Bot service account with a role-based access policy, kept separate from personal logins and auditable. Per Airbyte's tools page, direct reads use the credentials stored in the connector rather than the asking user, so source-side access is not per-user even though the tool calls are.

Some servers offer both and the default decides the outcome

Looker's source page says the Toolbox can pass the caller's OAuth token instead of one service credential via use_client_oauth, which defaults to false. With the default, identity is the API user configured with client_id and client_secret. The same Toolbox documents useClientOAuth for BigQuery, which forwards the client's OAuth token so calls run as the asking user, and impersonateServiceAccount for service account impersonation.

Omni lets an Organization API key run tools as another user through the X-MCP-User-ID header. Cube's API-key tokens can act as the key's owner, as another user, or be limited to specific tools, and last up to one hour with no refresh token. Tableau's self-hosted server offers PAT (the default), direct-trust, OAuth and passthrough authentication, per its configuration docs.

DataHub splits by transport. Per its README, the Docker HTTP deployment has each MCP client supply its own DataHub token, so permissions and audit identity are preserved per user, and the HTTP entry point refuses to start if a shared server-wide token is configured. Over stdio the README uses DATAHUB_GMS_URL and DATAHUB_GMS_TOKEN.

Personas narrow what an agent is shown

A persona is a named profile of what a role should see. Per Euno's docs, the server uses the active persona, and if none can be identified the user is asked to choose; the docs say the active persona scopes data and actions, and list_personas, current_persona and switch_persona are among the published tools. Per Atlan's security page, guests and members are scoped to their persona, and MCP narrows but never widens what a user's login permits.

OpenMetadata's reference lists get_persona_context and find_context, which serve shared AI context documents curated per persona, and get_user_context returns the caller's identity, roles, teams, domains and active persona, with no parameter to look up another user. These tools shape context. The access boundary in each case is the platform's own policy, as the vendors describe it.

Row-level security and role gates appear in the semantic and BI servers

Cube's docs name row-level security for MCP queries. Microsoft's overview says Fabric IQ, its consumption server, answers questions over semantic models and respects permissions, row-level security and object-level security. Microsoft's authoring server goes the other way: its tools manage security roles with row-level security inside the model, per the README.

Role gates are more common. Per Monte Carlo's docs, an Editor role or above is required to use the server. Hex requires the Explorer role for knowledge tools and Editor or above for project editing tools. Cube says a Viewer role or higher is needed and that data model editing tools show only for roles allowed to edit the model, Admin and Developer by default. Alation's remote server lists tools dynamically and filters out tools the current user cannot use. Snowflake's docs say access to the MCP server does not give access to tools, since privileges are granted per tool.

The documented identity of each server, side by side

The table records the identity each publisher says a call runs as. The sources for each row are listed at the end of the guide. Where a server offers more than one route, both are shown.

A row that reads none found means the page read on 10 Nov 2026 did not state how results are scoped. Per-user scoping also depends on the client and on how the customer configures roles, so the vendor's statement is the starting point for a test and not the end of it.

ServerIdentity the call runs asPer-user scoping documented
Atlan MCP (hosted)Signed-in user via OAuth, or API key as a shared identityYes, with OAuth
BigQuery remote MCP serverAuthenticated Google Cloud identity via OAuth 2.0 and IAMYes
Collibra MCP ServerServer-wide credential over stdio; client Basic Auth headers over HTTPPer request over HTTP
Cube MCP serverAuthenticated user, or API-key owner or chosen userYes, with row-level security
Fivetran MCP ServerOne API key and secretNot documented
Looker tools in MCP ToolboxAPI user, or caller's OAuth token if use_client_oauth is trueOpt-in
Select Star MCP ServerAPI token as Bearer headernone found on 10 Nov 2026
Tableau MCPHosted: each user's Tableau Cloud identity; self-hosted: PAT by defaultHosted only

Sources

  1. Atlan remote MCP overview, read 10 Nov 2026
  2. Atlan MCP security page, read 10 Nov 2026
  3. Cube MCP server docs, read 10 Nov 2026
  4. Omni MCP tools, read 10 Nov 2026
  5. Sigma MCP server help page, read 10 Nov 2026
  6. Tableau MCP repository, read 10 Nov 2026
  7. Tableau MCP environment variables, read 10 Nov 2026
  8. BigQuery remote MCP guide, read 10 Nov 2026
  9. Databricks managed MCP page, read 10 Nov 2026
  10. Fivetran MCP README, read 10 Nov 2026
  11. Secoda MCP docs, read 10 Nov 2026
  12. Select Star MCP docs, read 10 Nov 2026
  13. Collibra MCP README, read 10 Nov 2026
  14. Alation authentication guide, read 10 Nov 2026
  15. Alation agent SDK README, read 10 Nov 2026
  16. OpenMetadata MCP guide, read 10 Nov 2026
  17. OpenMetadata MCP reference, read 10 Nov 2026
  18. Airbyte MCP tools, read 10 Nov 2026
  19. MCP Toolbox Looker source, read 10 Nov 2026
  20. MCP Toolbox BigQuery source, read 10 Nov 2026
  21. DataHub MCP README, read 10 Nov 2026
  22. Euno MCP setup docs, read 10 Nov 2026
  23. Microsoft Learn MCP servers overview, read 10 Nov 2026
  24. Power BI Modeling MCP README, read 10 Nov 2026
  25. Monte Carlo MCP server docs, read 10 Nov 2026
  26. Hex MCP server docs, read 10 Nov 2026
  27. Snowflake-managed MCP docs, read 10 Nov 2026

Last reviewed 10 Nov 2026.