The Metric Insights Concierge service supports integration with external AI agents, such as Snowflake Intelligence or Databricks Genie, through a Model Context Protocol (MCP) server. By setting up this connection, Users can interact with these external agents directly from Concierge and request data that those agents have access to.
Review this article for a comprehensive overview of the different ways Concierge can interact with other AI-powered tools, the decisions that need to be made, and the specialists required to configure that interaction.
In this article:
- Connecting Concierge to External Resources
- Connecting External Tools to Metric Insights MCP Server
- Required Administrator Roles
- Prerequisites
Connecting Concierge to External Resources
Concierge can connect to any MCP server as an External Resource, provided the server meets these requirements:
- Transport protocols: The server must support Server-Sent Events (SSE) or another streamable HTTP transport, as defined in the MCP Transport Specification.
- Authentication: Authentication is configured by adding the required HTTP headers in the External Resource Configuration. For added security, tokens can be stored as encrypted variables.
Because Concierge includes its own MCP client, it works with any LLM API and doesn’t depend on the LLM provider to support MCP.
Available External Resources
The Metric Insights team has tested and configured connections with a number of external AI tools. See the following chapters for detailed information on setting them up:
- Databricks Genie MCP Server
- Snowflake Intelligence MCP Server
- Fabric Data Agent MCP Server
- WisdomAI MCP Server
- Sigma MCP Server
For more general description of the connecting to External Resource process, see the Connecting External Agents to Concierge via MCP Server article.
If your organization uses an AI tool that isn’t listed above, follow the Connecting Concierge to Custom External Resource step-by-step guide. However, use a built-in Resource Type whenever one is available, and choose “Other Resource” only when none fits. Built-in types include token handling and per-user OAuth with no extra setup.
Decision: Auth Type
Before you begin configuration process, decide what authentication method Concierge will use to connect to External Resource:
- Service Account Token: You provide the credentials for the external AI tool service account, and the token is requested and added to the configuration code automatically. However, when the token expires, you must run the Get Token action manually to renew it. Use this method if your account uses OAuth authentication.
- User OAuth: Works like Service Account Token, but applies the permissions of the user who sends the query to Concierge. Use this method when the external tool users have different levels of data access and those differences must carry over to their Concierge queries.
- Service Principal: You provide Microsoft Entra ID credentials, and MI requests the token and adds it to the configuration code automatically. The token stays valid as long as the Client Secret remains valid. Use this method if your company uses Microsoft Entra ID for identity management.
- Defined in configuration: You create the authentication token in your AI tool account and paste it into the Concierge configuration code manually. Use this method if your security model doesn’t support OAuth or has specific requirements that call for a more flexible setup.
Not every External Resource supports all of the listed authentication options. The list for each tool includes only the options that apply to it.
As a best practice, use a per-user token (User OAuth) instead of a shared service token whenever the platform supports it. That way, each user gets answers only from data they can already access on that platform.
Creating Domains
In Metric Insights, a Domain is an object that tells Concierge when to use connected External Resources. Each Domain represents a general topic. When a User asks a question about that topic, Concierge sends the request to the External Resources linked to that Domain. The relationship works both ways: one Domain can be linked to several External Resources, and one External Resource can be linked to several Domains.
The best practice is to model each Domain on a single business subject, mapped to a single space on the platform. Concierge uses Domains both to route questions and to decide who can see what. A Domain that covers two subjects confuses routing, and two Domains that point to the same space split that space’s Knowledge Graph learnings and metadata. Keep the mapping one-to-one: one subject, one platform space, one Domain.
Pitfalls to Avoid
- Inserting tokens directly into the configuration code. A token typed straight into the JSON shows up in exports, screenshots and support tickets. Keep credentials out of the config text: store tokens as encrypted Variables and reference them instead.
- Forgetting that tokens expire. With the “User OAuth” and “Service Account Token” Auth Types, tokens eventually expire and must be renewed manually. Only the “Service Principal” Auth Type avoids this. Treat every token as something that will expire, and plan for its renewal.
- Creating overly broad or overlapping Domains. Don’t create one big “Everything” Domain or several Domains for the same space.
Required Administrator Roles
| Role | Responsibilities |
|---|---|
| External Tool Administrator |
|
| Metric Insights Administrator |
|
Prerequisites
- Each external tool has its own list of prerequisites for connecting to Concierge:
- For Databricks Genie MCP Server:
- Databricks Admin Account;
- Ability to grant service principal the SELECT and USE SCHEMA privileges.
- For Snowflake Intelligence MCP Server:
- Snowflake accounts for all users who will run queries against Snowflake from Concierge must have a default role configured with the required set of permissions:
- USAGE: agent, database, schema, warehouse;
- Additionally, USAGE permission for MCP server and database, schema and all the tables connected to it.
- SELECT on the tables and semantic views (if applicable);
- READ on stages (if applicable);
- Microsoft Azure Administrator account for "Service Principal" Auth Type.
- Snowflake accounts for all users who will run queries against Snowflake from Concierge must have a default role configured with the required set of permissions:
- For Fabric Data Agent MCP Server:
- Microsoft Power BI Administrator account;
- Azure Administrator account;
- The Item.Execute.All permission for the Azure Fabric App.
- For Sigma MCP Server:
- A Sigma account type with the Use Sigma MCP with OAuth and other permissions enabld:
- Depending on the type of data source you want to use, you need the View connections, View data models, and/or View workbooks permissions.
- To search, explore, or query a specific document, you must be granted at least Can view access to the document.
- To search, explore, or query a specific connection, you must be granted at least Can use access to the connection.
- To call agents, you must be granted at least Can view access to a workbook that contains the agent.
- To build workbooks, you must be assigned an account type with the Create, edit, and publish workbooks and Create, edit, and publish workbooks with Sigma MCP permissions enabled.
- To edit an existing workbook, you must also be granted Can edit access to the workbook.
- To take a screenshot of a workbook page or element, you must be assigned an account type with the Create, edit, and publish workbooks with Sigma MCP permission enabled and be granted at least Can view access to the workbook.
- A Sigma account type with the Use Sigma MCP with OAuth and other permissions enabld:
- For Databricks Genie MCP Server:
- Metric Insights System Administrator account.