The Connection Management server lets AI agents create, manage, test, monitor, and validate connections to external systems with full CRUD operations over the connection metadata.
By exposing Data Integration controls, this MCP server enables your AI agent to learn a connector's attribute schema before building a connection. Agents operate only on the connections they are entitled to.
Key capabilities
This MCP server offers the following key capabilities:
•Connector discovery. Lists the connector types available to the organization and returns each connector's configuration schema so an agent can assemble a correct connection payload for any connector type.
•Runtime environment discovery. Lists the runtime environments that can run a connection. For toolkit connectors, resolves dynamic attribute option lists from a live agent.
•Connectivity testing. Validates a connection payload's connector-specific attributes and credentials against the live endpoint without persisting anything.
•Connection retrieval. Fetches connection metadata by identifier or name, or lists every connection visible in the caller's organization.
•Connection provisioning. Creates and updates connection definitions, guided by the discovery tools, so connector-specific attributes can be supplied correctly.
•Governed deletion. Removes connections. On request, cascades the removal of dependent tasks that reference them.
Use cases
Use this MCP server to address the following use cases:
•Guided connection creation. Discover a connector's required attributes and a valid runtime environment, tests the payload, and then creates the connection in one automated flow.
•Connection inventory. List every connection in an organization to report on the available Data Integration endpoints.
•Configuration lookup. Retrieve a connection by name to confirm its runtime environment before scheduling a task.
•Connectivity validation. Test a connection's credentials and attributes before creating or updating it as part of an onboarding workflow.
•Decommissioning. Delete an obsolete connection and its dependent tasks when retiring a data source.
Tools
The following table describes the tools available on this MCP server:
Tools
Description
create_connection
Creates a connection in your organization. The body is a single flat connection object. Set "@type":"connection". Don't use the get_connector_schema tree.
Perform the following steps to build a body:
1Before creating the body, validate it with test_connection.
2Use list_connector_types to identify the connector and pass its name as type.
3Use get_connector_schema to learn which attributes apply, which attributes are mandatory, and which attributes are secret. Also learn each attribute’s options and which subgroup branch to send for value-dependent attributes.
4Use list_connection_runtime_environments for a valid top-level runtimeEnvironmentId.
5For toolkit connectors, use resolve_dynamic_attributes to fill option-driven values. Place the following attributes at the top level:
- authenticationType
- codepage
- database
- host
- password
- port
- schema
- username
Only place connector-specific attributes with no first-class field inside connParams, keyed by the “name” attribute. The MCP server ignores any standard attributes in connParams. You might wish to mirror an existing connection of the same type from list_connections or get_connection_by_name. Never send the following parameters:
- agentGroupId
- agentId, if the server derived it
- orgId
delete_connection
Deletes a connection by its identifier. If the connection is still referenced, the MCP server won't the delete action unless you request a dependency cascade. Optionally, you can add a DeleteDependencies header.
get_connection
Retrieves a single connection by its unique identifier. A missing identifier returns a "not found" response.
get_connection_by_name
Retrieves a single connection by its unique name. A missing name returns a "not found" response.
list_connections
Lists all connections you can access in your organization, with secrets masked. Returns an empty list when none exist.
test_connection
Tests connectivity for a connection payload without persisting it. Use this tool to validate attribute placement and credentials before creating or updating a connection.
Supply the same flat connection body that you pass to create_connection. Include the following attributes in connParams:
- "@type":"connection"
- a top-level name
- type
- runtimeEnvironmentId
- the standard attributes at the top-level
- connector-specific attributes
Note the following restrictions:
- A resolvable runtime environment with an active agent is required because live connectivity runs through the connection's runtime environment.
- Secrets must be real plain text values for the test. For example, a masked ******* fails.
- Omitting required attributes or placing attributes in connParams instead of top-level result in a structure error like "Enter a valid user name" or "The password is empty."
test_connection_by_id
Tests connectivity for an existing connection by the connection's ID. Use this to reverify a connection you created or fetched without resupplying any attributes or connParams. Unlike test_connection, test_connection_by_id sends no body because the server itself loads any stored secrets.
Note the following restrictions:
- A resolvable runtime environment with an active agent is required because live connectivity runs through the connection's runtime environment.
- A failed check returns an error body with a code and description.
update_connection
Updates an existing connection in your organization. Sends the full connection body as a single flat connection object. Set "@type":"connection". Don't use the get_connector_schema tree.
Perform the following steps to build a body:
1Before creating the body, validate it with test_connection.
2Use list_connector_types to identify the connector and pass its name as type.
3Use get_connector_schema to learn which attributes apply, which attributes are mandatory, and which attributes are secret. You also learn each attribute’s options and which subgroup branch to send for value-dependent attributes.
4Use list_connection_runtime_environments for a valid top-level runtimeEnvironmentId.
5For toolkit connectors, use resolve_dynamic_attributes to fill option-driven values. Place the following attributes at the top level:
- authenticationType
- codepage
- database
- host
- password
- port
- schema
- username
Note:
In AI Agent Engineering, the MCP server tools are called "actions."