Adding a custom MCP server¶
As an administrator, you can connect any MCP server not already in the catalog by providing its URL. This is useful for internal tools, custom integrations, or servers that aren’t yet listed in the Tools catalog.
Requirements¶
Currently, only users with the ACCOUNTADMIN role can administer MCP servers in Tools, including adding custom servers.
The server must:
- Support streamable HTTP transport with an endpoint ending in
/mcp - Support OAuth
Add a custom MCP server¶
- Sign in to Snowsight.
- Select AI Gateway.
- Select MCP & Tools. Tools opens in a new tab.
- Select Add app > Remote URL.
- Enter the server URL. The URL must end with
/mcp. - Enter an app name.
- Select Save.
After saving, follow the standard steps to enable the server for your users. See Distributing access to MCP servers.
Connection URL and identifier¶
The default identifier for a custom server is custom-{appName}, where {appName} is the name you gave the app in lowercase with hyphens replacing spaces. For example, an app named My Internal Tool gets the identifier custom-my-internal-tool.
After an administrator enables the server and grants the SNOWFLAKE$OPS.MCP$USER database role to the account roles that have server access, CoCo Desktop and CLI discover it automatically. Users still complete any required authorization.
For other MCP clients, users select AI Gateway > MCP & Tools in Snowsight, then select MCP Connections in the new tab. Find the server to view its connection URL and client instructions.
See Adding an MCP server to your AI client for instructions on adding this URL to a specific client.