From e4cfc849a6ea77d48bbacd8fa07da1f077b439eb Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 15 Jul 2026 00:41:31 +0000 Subject: [PATCH] docs: document Bearer PAT header for MCP --- references/integrations/lightdash-mcp.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/references/integrations/lightdash-mcp.mdx b/references/integrations/lightdash-mcp.mdx index 629753db..5f5e7b9e 100644 --- a/references/integrations/lightdash-mcp.mdx +++ b/references/integrations/lightdash-mcp.mdx @@ -229,7 +229,7 @@ If you're building your own agents or automated workflows, you can integrate dir - **Transport**: Lightdash MCP exposes a StreamableHTTP transport endpoint at `https://.lightdash.cloud/api/v1/mcp` - **Debugging**: Use `@modelcontextprotocol/inspector` to inspect and debug the MCP connection -- **Authentication**: For interactive setups use OAuth 2.0. For headless agents and automated workflows, you can authenticate with a Personal Access Token by passing `Authorization: ApiKey ` instead. Create the token under **Settings → Personal access tokens** for the user whose permissions and attributes you want the integration to use. Service account tokens are also supported on plans that include them. +- **Authentication**: For interactive setups use OAuth 2.0. For headless agents and automated workflows, you can authenticate with a Personal Access Token by passing it in the `Authorization` header — both `Authorization: ApiKey ldpat_` and `Authorization: Bearer ldpat_` are accepted on the MCP endpoint and resolve to the same PAT authentication path (the `Bearer` alias is MCP-only; no other Lightdash API endpoint changes auth behavior). Use `Bearer` when your MCP host only supports static `Bearer` tokens (e.g. Claude managed agents and other third-party MCP hosts that don't let you choose a custom auth scheme); use `ApiKey` for direct HTTP clients where you can set the scheme yourself, since it makes it explicit that the token is a Lightdash PAT. Create the token under **Settings → Personal access tokens** for the user whose permissions and attributes you want the integration to use — no changes to how PATs are generated, scoped, or expired, an existing token works. Service account tokens are also supported on plans that include them. - **Documentation**: See the [MCP specification](https://modelcontextprotocol.io/docs) for implementation details - **Pin a project (optional)**: pass `X-Lightdash-Project: ` to scope the MCP session to a specific project, skipping the `set_project` step. See [details below](#pin-a-project-with-the-x-lightdash-project-header). - **Override user attributes per request (optional)**: pass `X-Lightdash-User-Attributes: ` to override the authenticated user's attributes for that request (useful for row-level security when an agent acts on behalf of different end-users). See [details below](#override-user-attributes).