DROP MCP SERVER¶

Syntax¶

DROP MCP SERVER [ IF EXISTS ] <name>

Parameters¶

name

Specifies the identifier for the MCP server to drop.

If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

For more information, see Identifier requirements.

Access control requirements¶

A role used to execute this operation must have the following privileges at a minimum:

The USAGE privilege on the parent database and schema are required to perform operations on any object in a schema. Note that a role granted any privilege on a schema allows that role to resolve the schema. For example, a role granted CREATE privilege on a schema can create objects on that schema without also having USAGE granted on that schema.

For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.

For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

Usage Notes¶

• When the IF EXISTS clause is specified and the target object doesn’t exist, the command completes successfully without returning an error.

• Dropping an MCP server removes the server object and its tool configurations. Any MCP clients currently connected to the server will lose access.

• The underlying objects referenced by the MCP server tools (Cortex Search Services, Cortex Agents, UDFs, stored procedures) are not affected by dropping the MCP server.

Examples¶

The following example drops the MCP server named my_mcp_server:

DROP MCP SERVER my_mcp_server;

+----------------------------------------+
| status                                 |
|----------------------------------------|
| MY_MCP_SERVER successfully dropped.    |
+----------------------------------------+

The following example drops the MCP server named my_mcp_server if it exists:

DROP MCP SERVER IF EXISTS my_mcp_server;