MCP Server Setup Instructions

​

Prerequisites for setting up the Validio MCP Server

• In your Validio Workspace Settings, 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.

​

Connecting any MCP client

• 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

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

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

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

​

Microsoft 365 Copilot

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.

​

GitHub Copilot

​

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.

{
  "servers": {
    "validio": {
      "type": "http",
      "url": "https://your-validio-instance/mcp"
    }
  }
}

​

GitHub Copilot 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.

​

Snowflake

• 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

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

   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.

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;

​

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 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.

​

Troubleshooting

​

The MCP server URL returns a “not found” error

​

The client asks for a client ID and client secret

​

The client asks me to sign in again

​

The browser shows an invalid_client error when I sign in

​

The Validio tools don’t appear in GitHub Copilot

​

The Validio connector doesn’t appear in Snowflake

​

The CoCo CLI shows “Browser action timed out”