Connecting External Agents to Concierge via MCP Server

Concierge supports integration with external AI agents, such as Snowflake Intelligence or Databricks Genie, through the Model Context Protocol (MCP) Server. By setting up this connection, Users can seamlessly access and interact with these external agents directly from Concierge.

This article describes how to connect external AI agents to Concierge using MCP Server.

1. Open Concierge Setup Page

Access Admin > System > Concierge Setup

Open the Content Sources tab and scroll to the bottom of the page to find the External Resource Configuration section. 

Click [+ Add External Resource Configuration].

2. Configure External Resource

  1. Name: Give the External Resource a unique name.
  2. Add the code for connecting to your MCP Server.  A detailed description of what can go into this code box can be found in the next step below.
    Note: The code must be written in well formed JSON.
  3. Variables: Add Variables if needed.  In version 7.1.2, all variables are encrypted.
  4. [Save]

2.1. External Resource Code 

{
    "name": "3rd_party_agent",
    "title": "External agent",
    "display": "raw",
    "scope": "Questions about humsters",
    "scenario_type":"mcp_single_tool",
    "mcp_server": {
        "url": "http://ai.metricinsights.com:8009/mcp",
        "name": "snowflake-int"
    },
    "tool": "ask",
    "display_progress": "{{title}} : {{progress | int}}/{{total | int}} {{message}}",
    "timeout": 600
}

Sample code for connecting to a Snowflake Intelligence MCP server.  Remember this must be in well formed JSON.

Code Purpose
name The resource name. It has to be the same as the name entered in the Name field of the Edit External Resource Configuration.
title The display name. This name is shown in the All Sources button and in Concierge responses.
display Defines how data from the external agent is shown.
display
options		 raw In this mode, data is displayed exactly as received from the external agent.
llm In this mode, Concierge uses an LLM to reformat the external agent’s data for display.
template In this mode the User has to add a template row below and add the code for the template. That template will be used for data display.
icon This icon is shown in the All Sources button and in Concierge responses. Use the name of the icon from MI Development Icons Library: https://[hostname]/dev/icons
template The response template code, required if display is set to template. See above.
llm_comment Provides progress commentary from Concierge. This row is used only when display is set to raw or template.
Available options: true or false.
scope A prompt that instructs the LLM when to use this external resource.
NOTE: if using Domains, all Domain IDs must be listed in this scope.
scenario_type Specifies how Concierge will interact with the external resource.
scenario_type
options		 mcp_single_tool

Maps intention parameters directly to a single MCP tool call.

  • Fastest response.
  • Requires a tool row specifying which tool to use.
mcp_agent

Triggers a dedicated agent with its own execution loop.

  • Can run multiple MCP tool calls sequentially.
  • Useful for complex tasks but slower and less predictable.
mcp_one_shot or mcp_1shot_server

Executes a single MCP tool call for the entire request.

  • Simpler setup—does not require defining each tool individually.
  • Attaches the usage scope to the whole MCP server.
  • Requires an extra LLM request to select the tool.
mcp_server

Contains options, defining server connection.
mcp_server options url
 URL of the MCP Server.
name
 Name of MCP Server.
transport
 Defines MCP Transport type. Available options are streamable-http and sse. This field is optional. If it is not set, it will be autodetected.
auth
 This field contains http headers with their values necessary for authentication. 
tool The name of the tool to use for this resource, if scenario_type is set to mcp_single_tool.
display_progress The template for displaying MCP execution progress status messages from the MCP server if available.
timeout Timeout in seconds. If the external resource does not respond within this time, Concierge shows an error message.

3. Add Domain

The external resource won't appear in the All Sources list unless the User connects a Domain to it.

  1. In the external resource row click the Domains number to open the Associated Domains for window.
  2. [+ Add Associated Domain]
  3. Domain Name and Domain ID: Select a Domain from the dropdown list and enter the corresponding Domain ID.
  4. [Save]
  5. [OK]

After that give the system about 15 seconds to update, refresh the page and after that the new external resource will appear in the All Sources menu.