> ## Documentation Index
> Fetch the complete documentation index at: https://docs.validio.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server Setup Instructions

> Step-by-step instructions for connecting Antigravity CLI, Claude, Microsoft Copilot, Snowflake, and other MCP clients to the Validio MCP Server using OAuth authentication and Streamable HTTP transport.

Connect to our MCP server natively in Claude, Antigravity CLI, Microsoft Copilot, Snowflake, and various other MCP clients. Validio's MCP server supports HTTP-based transport (Streamable HTTP) with OAuth authentication and dynamic client registration.

The Validio MCP server will inherit the permissions and access of the user account you use to connect to it.

> [!NOTE]
>
> The Validio MCP server provides tools for managing resources, such as sources, validators, and incidents. Read more about key benefits in [Validio MCP Server](https://docs.validio.io/docs/integrations/validio-mcp-server.md). For detailed examples and use cases, see [MCP Server User Guide](https://docs.validio.io/docs/integrations/validio-mcp-server/mcp-server-user-guide.md).

## Prerequisites for setting up the Validio MCP Server

![The Validio Workspace Settings AI Features section, showing the Enable MCP Server option](https://mintcdn.com/validio/h4NQPs1kJwlpB1Yj/images/docs/integrations/900-mcp-server-setup.png?fit=max\&auto=format\&n=h4NQPs1kJwlpB1Yj\&q=85\&s=bb39fe334a06ca8cc5b5c113519bb73f)

AI Features settings with Enable MCP Server checked

Before you connect a client:

* In your [Validio Workspace Settings](https://docs.validio.io/docs/access-and-settings/settings/workspace-settings.md), configure the **Application URL**. The Application URL is the URL to your Validio installation: `https://your-validio-instance`.
* In the same settings, under **AI features**, check **Enable MCP server**.
* Note your **MCP server URL**, which every client below connects to. It's your Application URL followed by `/mcp`, for example: `https://your-validio-instance/mcp`.

Then choose your client to jump to its setup instructions:

> **[Antigravity CLI](#antigravity-cli)**
>
> Add Validio as an HTTP MCP server from the command line and authenticate in your browser.

> **[Claude](#claude)**
>
> Add Validio as a custom connector in Claude.ai and Claude Desktop, or as an MCP server in Claude Code.

> **[Microsoft Copilot](#microsoft-copilot)**
>
> Use Validio in Microsoft 365 Copilot through a Copilot Studio agent, or in GitHub Copilot in VS Code and the Copilot CLI.

> **[Snowflake](#snowflake)**
>
> Connect Validio to Snowflake CoCo, Cortex Agents, and Snowflake CoWork.

For any other client, see [Connecting any MCP client](#connecting-any-mcp-client).

***

## Connecting any MCP client

The sections below cover the most common clients. You can also connect any other MCP client that meets these requirements:

* **Remote MCP servers over Streamable HTTP.** Add Validio as a remote (HTTP) server using your MCP server URL. Validio is a remote server only, with no local (stdio) version, and doesn't support the older SSE transport.
* **OAuth with dynamic client registration.** When the client asks how to authenticate, choose OAuth with automatic or dynamic client registration. The client registers itself with Validio, so you don't need a client ID or client secret. Validio doesn't issue client IDs and secrets to enter manually.
* **Browser sign-in.** The first time the client connects, it opens a browser window where you log in to Validio with your user account. The connection inherits that user's permissions.
* **Sign in right away.** Validio removes a client registration if no one signs in with it shortly after it's created. Finish the browser sign-in as soon as the client prompts you.

***

## Antigravity CLI

> [!NOTE]
>
> Antigravity CLI replaces Gemini CLI, which Google retired in June 2026. If you previously connected Validio through Gemini CLI, set up the connection again in Antigravity CLI.

In the CLI,

1. Run `agy mcp add validio --type http https://your-validio-instance/mcp`
2. Start Antigravity by running `agy`,
   1. Run `/mcp` to list all MCP servers. The Validio MCP server shows as `Unauthorized [Auth Needed]`.
   2. Select `validio`, press `Enter` to open **Actions**, and choose the authenticate option.
   3. In your browser, log in to Validio with your user account.
3. Run `/mcp` again to confirm that the Validio MCP server is connected and its tools are listed.

***

## Claude

### Claude.ai and Claude Desktop

On web or desktop,

1. Navigate to **Admin Settings > Connectors**.
2. Click **Add custom connector** and in the dialog:
   1. **Name**: Give the connector a name.
   2. **Remote MCP server URL**: Enter your Validio MCP server URL, which will have the format `https://your-validio-instance/mcp`.
   3. Click **Add**.
3. In **Settings > Connectors**,
   1. Connect to the Validio MCP server.
   2. When prompted, log in to Validio with your user account and password.
4. In a new Claude chat, open the **Search and tools** menu and enable the new connector.

### Claude Code

In the CLI,

1. Run `claude mcp add validio -t http https://your-validio-instance/mcp`
2. Open a Claude Code session,
   1. Run `/mcp` to list all MCP servers.
   2. Select the Validio MCP server and go through the authentication flow.

***

## Microsoft Copilot

You can use Validio in Microsoft 365 Copilot through a Copilot Studio agent, and in GitHub Copilot in Visual Studio Code and the Copilot CLI.

### Microsoft 365 Copilot

Add the Validio MCP server as a tool to an agent in Microsoft Copilot Studio, then publish the agent to Microsoft 365 Copilot. You need access to a Copilot Studio environment where you can create agents.

1. Add the Validio MCP server to your agent in Copilot Studio:
   1. Open your agent and go to the **Tools** page.
   2. Select **Add a tool** > **New tool** > **Model Context Protocol**.
   3. **Server name**: Give the server a name, for example `Validio`.
   4. **Server description**: Describe what the server does, for example `Validio data quality: sources, validators, incidents, and lineage`. The agent uses this description to decide when to call Validio.
   5. **Server URL**: Enter your Validio MCP server URL, `https://your-validio-instance/mcp`.
   6. For authentication, select **OAuth 2.0**, and set **Type** to **Dynamic discovery**.
   7. Select **Create**, then **Next**.
2. In the **Add tool** dialog, select **Create a new connection**, and log in to Validio with your user account when prompted.
3. Select **Add to agent**.
4. Publish the agent, then make it available in Microsoft 365 Copilot:
   1. Go to **Channels** > **Teams and Microsoft Copilot**.
   2. Keep **Make agent available in Microsoft Copilot** selected, and select **Add channel**.
   3. To share the agent with your organization, use **Availability options**. Making the agent available to everyone in your organization requires approval from your Microsoft 365 admin.
5. In Microsoft 365 Copilot, type **@** and select your agent to start using Validio.

Copilot Studio connects to MCP servers through Power Platform connectors, so any data policies your organization applies to connectors also apply to the Validio MCP server.

For information, refer to [Microsoft Copilot Studio: Connect your agent to an existing MCP server](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent) and [Microsoft Copilot Studio: Connect and configure an agent for Teams and Microsoft 365 Copilot](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams).

### GitHub Copilot

> [!NOTE]
>
> For Copilot Business and Copilot Enterprise, an organization or enterprise owner must enable the **MCP servers in Copilot** policy before members can use MCP servers. If the policy restricts access to **Registry only**, the Validio MCP server must also be added to your organization's MCP registry. For information, refer to [GitHub Docs: Configuring MCP server access](https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-server-access).

#### Visual Studio Code

1. Open the Command Palette and run **MCP: Add Server**.
2. Choose the HTTP server type, enter your Validio MCP server URL, `https://your-validio-instance/mcp`, and name the server `validio`.
3. Choose where to save the configuration, for example your user configuration or the current workspace.
4. When VS Code starts the server, it opens a browser window. Log in to Validio with your user account.
5. In the Chat view, select **Agent** mode, then select **Configure Tools** to confirm that the Validio tools are enabled.

Alternatively, add the server directly to your `mcp.json` file:

```json title="JSON" theme={null}
{
  "servers": {
    "validio": {
      "type": "http",
      "url": "https://your-validio-instance/mcp"
    }
  }
}
```

For information, refer to [Visual Studio Code: Use MCP servers](https://code.visualstudio.com/docs/copilot/customization/mcp-servers).

#### GitHub Copilot CLI

In the CLI,

1. Run `copilot mcp add --transport http validio https://your-validio-instance/mcp`
2. Start a session by running `copilot`,
   1. Run `/mcp auth validio` to sign in.
   2. In your browser, log in to Validio with your user account.
3. Run `/mcp` to confirm that the Validio MCP server is connected and its tools are listed.

Alternatively, in a session, run `/mcp add`, set **Server Type** to **HTTP**, enter your Validio MCP server URL, and press `Ctrl+S` to save.

For information, refer to [GitHub Docs: Adding MCP servers for GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers).

***

## Snowflake

You can connect Validio to Snowflake's AI products: Snowflake CoCo (formerly Cortex Code), Snowflake's coding agent, and Cortex Agents and Snowflake CoWork (formerly Snowflake Intelligence). Validio connects in two ways:

* **Account connector (recommended)**: An admin sets up Validio once for your Snowflake account. The connector reaches CoCo in Snowsight, Cortex Agents, and Snowflake CoWork for every role that's granted access.
* **Local setup**: CoCo Desktop and the CoCo CLI don't use the account connector. Each developer adds Validio on their own machine.

### CoCo in Snowsight, Cortex Agents, and Snowflake CoWork

To create the connector, you need the `ACCOUNTADMIN` role, or privileges to create an API integration and an external MCP server in your Snowflake account.

1. Add Validio as a custom MCP connector in Snowsight:
   1. As `ACCOUNTADMIN`, select your user icon in the bottom-left corner of Snowsight, then select **Settings**. Under **Account**, select **MCP Connectors**, then select **Add custom**.
   2. Choose a database and schema, and give the connector a name, for example `VALIDIO`.
   3. Select the **Dynamic Client Registration (DCR)** tab, and enter only your Validio MCP server URL in **Server URL**.
   4. Select **Add**, then connect and log in to Validio with your user account right away.

2. Grant `USAGE` on the MCP server and its API integration to the roles that should use Validio:

   ```sql title="SQL" theme={null}
   GRANT USAGE ON EXTERNAL MCP SERVER my_db.my_schema.validio TO ROLE my_role;
   GRANT USAGE ON INTEGRATION validio_mcp_integration TO ROLE my_role;
   ```

   To find the name of the API integration, run `DESCRIBE EXTERNAL MCP SERVER my_db.my_schema.validio;`.

3. To use Validio in a Cortex Agent, add the connector to the agent:
   1. In Snowsight, go to **AI & ML** > **Agents**, and select the agent.
   2. Open **MCP Connectors**, find Validio under **Available Connectors**, and select **Add to agent**.

4. Each user connects once with their own Validio account. After that, the Validio tools stay available in later conversations.
   * **CoCo in Snowsight**: In the CoCo composer, select **+** to open **MCP Connectors**, select Validio, and log in to Validio with your user account.
   * **Snowflake CoWork**: Open the sources panel, select **Connectors**, and select **Connect** next to Validio. Log in to Validio with your user account. The connector shows as **Connected**.

Alternatively, create the connector with SQL:

```sql title="SQL" theme={null}
CREATE API INTEGRATION validio_mcp_integration
  API_PROVIDER = external_mcp
  API_ALLOWED_PREFIXES = ('https://your-validio-instance/mcp')
  API_USER_AUTHENTICATION = (
    TYPE = OAUTH_DYNAMIC_CLIENT
    OAUTH_RESOURCE_URL = 'https://your-validio-instance/mcp'
  )
  ENABLED = TRUE;

CREATE EXTERNAL MCP SERVER my_db.my_schema.validio
  WITH DISPLAY_NAME = 'Validio'
  URL = 'https://your-validio-instance/mcp'
  API_INTEGRATION = validio_mcp_integration;
```

Creating the MCP server requires the `CREATE EXTERNAL MCP SERVER` privilege on the schema.

Users only see the Validio connector when their active role has `USAGE` on it. `USAGE` makes the connector visible, but Snowflake grants tool permissions separately, so check them if tool calls fail. Snowflake supports tools from external MCP servers, but not resources or prompts.

Snowflake traces each Validio tool call in the agent's **Observability** tab. To cut off access to Validio, disable the API integration.

For information, refer to [Snowflake Documentation: MCP connectors](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors) and [Snowflake Documentation: CoCo in Snowsight MCP connectors](https://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight/mcp-connectors).

### CoCo Desktop

In CoCo Desktop,

1. Go to **Settings** > **MCP**, select **+ New**, and choose **Remote (HTTP)**.
2. Give the server a name, for example `validio`, and enter your Validio MCP server URL.
3. Select **Connect**, then select **Open** on the browser prompt and log in to Validio with your user account.
4. Confirm that a green dot shows next to the server and its tools are listed. Send a new message so the agent picks up the Validio tools.

CoCo Desktop and the CoCo CLI share one local configuration. Removing the Validio MCP server in one removes it from the other.

### CoCo CLI

> [!WARNING]
>
> The CoCo CLI can't currently complete sign-in with Validio. Connecting fails with the error `redirect_uris can hold at most 10 URIs`. Until this is resolved, use [CoCo in Snowsight](#coco-in-snowsight-cortex-agents-and-snowflake-cowork) or [CoCo Desktop](#coco-desktop).

In the CLI,

1. Run `cortex mcp add validio https://your-validio-instance/mcp --transport http`
2. Run `cortex mcp start`. CoCo opens your browser. Log in to Validio with your user account.
3. Confirm that the output lists the Validio MCP server under **Connected Servers** with its tools available.

To list or remove configured servers, run `cortex mcp list` or `cortex mcp remove validio`.

For information, refer to [Snowflake Documentation: CoCo CLI MCP support](https://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-mcp).

***

## Troubleshooting

### The MCP server URL returns a "not found" error

Check that **Enable MCP server** is checked under **AI features** and that the **Application URL** is configured in your [Validio Workspace Settings](https://docs.validio.io/docs/access-and-settings/settings/workspace-settings.md). The MCP server is unavailable until both are set.

### The client asks for a client ID and client secret

Validio doesn't issue client IDs and secrets. Choose the client's automatic or dynamic client registration option instead, such as **Dynamic discovery** in Microsoft Copilot Studio or `OAUTH_DYNAMIC_CLIENT` in Snowflake.

### The client asks me to sign in again

Sign-ins expire after a period of time. Re-authenticate through your client when prompted, and log in to Validio with your user account.

### The browser shows an `invalid_client` error when I sign in

The client is using a registration that Validio has already removed, which happens when a sign-in isn't finished shortly after the client registers. Remove the Validio MCP server from your client, add it again, and finish the browser sign-in right away. In CoCo Desktop, quit the app fully before you add the server again.

### The Validio tools don't appear in GitHub Copilot

Check that the **MCP servers in Copilot** policy is enabled for your organization or enterprise, and that tools are enabled under **Configure Tools** in the Chat view.

### The Validio connector doesn't appear in Snowflake

Check that your active role has `USAGE` on both the Validio external MCP server and its API integration. If the connector appears but tool calls fail, check the role's tool permissions in Snowflake.

### The CoCo CLI shows "Browser action timed out"

This timeout comes from the Snowflake sign-in, not from Validio. Finish signing in to Snowflake in your browser, then try again.