> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloud.cdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Management MCP > The Management MCP server exposes administrative tools for inspecting available data sources and managing connections through any MCP-compatible client. Use it to programmatically list, create, and test connections rather than working through the Connect AI UI. The Management MCP is available for the Connect AI Developer edition only. To use the Management MCP from a supported client tool, add the following URL to the **Remote MCP Server URL** field: *[https://mcp.cloud.cdata.com/mcp/mgmt](https://mcp.cloud.cdata.com/mcp/mgmt)*. Once you are connected, you can ask natural-language questions that drive the management tools, or invoke the tools directly via `tools/call`. ## Authentication The Management MCP server uses the same authentication options as the data MCP server. See [Authentication](/en/API/Authentication) for details. ## Management MCP Tools The Management MCP server exposes the following tools. Invoke them via `tools/call` with the tool name and an `arguments` object matching the input parameters below. ### Connection Management #### create\_connection Save a new data source connection. Required property names depend on the source and come from `get_source_properties`. If the source uses OAuth (for example, Google Sheets or Salesforce), the response includes a link the user opens in their browser to sign in and finish setup. **Parameters** * `name` (string, required)–short, human-friendly name shown in the user's connection list. * `source` (string, required)–internal source name from `list_available_sources`. * `properties` (object, required)–string/string map of configuration values keyed by the field names from `get_source_properties`. **Returns:** The created connection object, including its new `id`. For OAuth sources, also includes the sign-in URL the user must open. *** #### get\_source\_properties Describe the configuration fields a given data source accepts, such as URLs, credentials, and options. The response is split into `basic` fields (shown first) and `advanced` fields grouped by category. For fields with a fixed set of values (such as an authentication method), the response lists the allowed values and the follow-up fields each value unlocks. Call this before `create_connection`. **Parameters** * `source` (string, required)–the internal source name returned by `list_available_sources` (for example, `"JIRA"`, `"Salesforce"`, `"Snowflake"`). **Returns:** Object with `basic` and `advanced` field descriptors, including each field's name, type, required flag, allowed values, and conditional follow-up fields. *** #### list\_available\_sources List the data sources the user can connect to (for example, Salesforce, Snowflake, Jira). Call this before `create_connection` to confirm a source is available. **Parameters:** None **Returns:** Array of source entries with the internal `source` name (pass this to other tools), display name, version, and category. *** #### list\_connections List the data source connections the user has already saved. Use this to look up the connection `id` needed by `test_connection` or `add_tool_to_toolkit`. **Parameters:** None **Returns:** Array of connection objects, each with `id`, `name`, and source type. *** #### test\_connection Verify that a saved connection actually works by attempting to connect to the data source. Use this after `create_connection`, after the user finishes an OAuth sign-in, or when a previously working connection has started failing. **Parameters** * `id` (string, required)–the connection `id` returned by `list_connections`. **Returns:** Success message, or a specific error the user can act on. *** ### Toolkit Management #### add\_tool\_to\_toolkit Attach an existing connection to a toolkit, making its data operations available to the toolkit's MCP server. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `connection_id` (string, required)–the `id` of the connection to add, from `list_connections`. **Returns:** The new toolkit tool entry, including the connection name, source type, and default enabled operations. *** #### create\_toolkit Create a new empty toolkit. After creation, use `add_tool_to_toolkit` to populate it with connections. **Parameters** * `name` (string, required)–short, human-friendly name for the toolkit. * `server_instructions` (string, optional)–natural-language guardrails surfaced to MCP clients connecting to this toolkit. **Returns:** The created toolkit object, including its new `id`. *** #### get\_toolkit Fetch a toolkit's full state, including its name, server instructions, isActive status, and MCP remote connection info. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. **Returns:** Toolkit object with `id`, `name`, `serverInstructions`, `isActive`, and MCP remote info. *** #### get\_toolkit\_tool Fetch one connection's full state within a toolkit, including the connection name, enabled operations, and per-operation instructions. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `tool_id` (string, required)–the `id` of the toolkit tool, from `list_toolkit_tools`. **Returns:** Toolkit tool object with connection name, source type, enabled operations, and instructions. *** #### list\_custom\_tools List custom SQL tools across all connections inside a toolkit. Optionally filter to one connection. SQL bodies are not included. Use the admin UI to edit a tool's SQL. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `tool_id` (string, optional)–the `id` of the connection inside the toolkit, from `list_toolkit_tools`; omit to return custom tools from all connections. **Returns:** Array of custom SQL tool objects, each with `id`, name, description, active status, and parameter count. *** #### list\_toolkit\_tools List the connections currently inside a toolkit. Use this to look up `tool_id` values needed by `get_toolkit_tool`, `set_tool_op_enabled`, and similar operations. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. **Returns:** Array of toolkit tool entries, each with `id`, connection name, source type, and enabled operations. *** #### list\_toolkits List the toolkits the user has saved. Use this to look up `toolkit_id` values needed by other toolkit operations. **Parameters:** None **Returns:** Array of toolkit objects, each with `id`, `name`, and `isActive` status. *** #### rename\_toolkit Change a toolkit's display name. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `name` (string, required)–the new display name. **Returns:** Updated toolkit object with the new name. *** #### set\_all\_tool\_ops\_enabled Bulk enable or disable every operation of one kind for a connection inside a toolkit. To toggle a single operation instead, use `set_tool_op_enabled`. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `tool_id` (string, required)–the `id` of the toolkit tool, from `list_toolkit_tools`. * `kind` (string, required)–`"universal"` for built-in SQL ops or `"source"` for driver-specific ops. * `enabled` (Boolean, required)–`true` to enable all operations of that kind, `false` to disable them. **Returns:** Updated toolkit tool object reflecting the new operation states. *** #### set\_custom\_tool\_active Activate or deactivate one custom SQL tool within a toolkit. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `custom_tool_id` (string, required)–the `id` of the custom tool, from `list_custom_tools`. * `active` (Boolean, required)–`true` to activate, `false` to deactivate. **Returns:** Updated custom tool object with the new active status. *** #### set\_tool\_op\_enabled Enable or disable a single operation on one connection inside a toolkit. To toggle every operation of a kind at once, use `set_all_tool_ops_enabled`. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `tool_id` (string, required)–the `id` of the toolkit tool, from `list_toolkit_tools`. * `kind` (string, required)–`"universal"` for built-in SQL ops (for example, `execute_select`) or `"source"` for driver-specific ops (for example, `get_issue`). Use `get_toolkit_tool` to see which kind each op belongs to. * `op_name` (string, required)–the op name as shown in `get_toolkit_tool`. * `enabled` (Boolean, required)–`true` to enable, `false` to disable. **Returns:** Updated toolkit tool object. *** #### set\_toolkit\_active Activate or deactivate a toolkit. Deactivating hides the toolkit from MCP clients (requests return a 423 error) without deleting it. To permanently delete a toolkit, use the admin UI. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `active` (Boolean, required)–`true` to activate, `false` to deactivate. **Returns:** Updated toolkit object with the new `isActive` status. *** #### update\_source\_tool\_instructions Replace the per-source-op AI instructions surfaced to the LLM when a source tool is invoked. Source ops only. Universal ops have no per-op instructions. Pass an empty string to clear. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `tool_id` (string, required)–the `id` of the toolkit tool, from `list_toolkit_tools`. * `source_op_name` (string, required)–the source op name as shown in `get_toolkit_tool` (for example, `"get_issue"`). * `instructions` (string, required)–the replacement instruction text. Pass an empty string to clear. **Returns:** Updated toolkit tool object with the new instructions. *** #### update\_toolkit\_server\_instructions Replace the natural-language server-instructions text for a toolkit. The LLM reads these instructions when it first connects to the toolkit's MCP server. **Parameters** * `toolkit_id` (string, required)–the `id` of the toolkit, from `list_toolkits`. * `server_instructions` (string, required)–natural-language guardrails surfaced to MCP clients connecting to this toolkit. **Returns:** Updated toolkit object with the new server instructions. ## Suggested Prompts To get the most out of the Management MCP, use specific prompts that name the source or connection you want to act on. For example: * "List every connection I have, and group them by source type." * "What data sources can I connect to right now?" * "Show me the required properties I need to provide to connect to Salesforce." * "Create a new Salesforce connection named *Sales Prod* using OAuth." * "Test the *Sales Prod* connection and tell me if anything is failing." * "Create a new toolkit called *Sales Tools*, add my Salesforce connection to it, and give me the URL to connect my MCP client." * "Set the server instructions for *Sales Tools* to 'Read-only access to sales data. Do not modify any records.'" * "Show me everything in the *Sales Tools* toolkit, including which connections are in it and which operations are enabled."