Skip to main content
Connect AI Embed administrators can scope MCP access to a single connection by constructing a per-connection endpoint URL (https://mcp.cloud.cdata.com/mcp/connections/{connectionId}), and then using that endpoint in their applications to connect to users’ data. This is recommended for limiting the end user’s data access. The same URL is returned in the mcpUrl field of the List Connections response, so administrators can read it directly rather than constructing it. Administrators can also enter the generic URL https://mcp.cloud.cdata.com/mcp. However, this does not limit which connections an MCP session can access.

​
Authentication

Connect AI Embed supports OAuth JWT bearer token authentication. When using a per-connection endpoint, the JWT bearer token must include a connection_ids claim in addition to the other required claims. See Authentication for details.

​
MCP Tools

LLMs depend on the use of data resources to return data. The Connect AI MCP Server uses both universal and source tools to provide data in response to natural-language questions. Universal MCP tools include:
  • get_catalogs—retrieve a list of available database catalogs from Connect AI Embed.
  • get_schemas—retrieve database schemas from Connect AI Embed for a specific catalog. Schemas organize tables and stored procedures within a catalog.
  • get_tables—retrieve database tables from Connect AI Embed for a specific catalog and schema.
  • get_columns—retrieve a list of available database columns from Connect AI Embed for a specific catalog, schema, and table. This resource examines the table structure and column definitions.
  • query_data—execute SQL queries against the connected data sources and retrieve results.
  • get_procedures—retrieve stored procedures from Connect AI Embed for a specific catalog and schema. Stored procedures contain executable SQL logic within a schema.
  • get_procedure_parameters—retrieve parameter metadata for stored procedures from Connect AI Embed for a specific catalog, schema, and procedure. Parameter metadata includes names, data types, and directions required for proper procedure execution.
  • execute_procedure—execute the stored procedure for the chosen catalog and schema.
Source tools depend on the data source. For example, the Jira data source contains MCP tools such as Create Issue, Search Issues, Update Issue, and Add Comment.

​
Suggested Prompts

To get the most out of MCP integration tools, use specific, detailed prompts. If your prompts are ambiguous, the client tool, such as Microsoft Copilot Studio or Claude, may ask follow-up questions to clarify the data you want to retrieve. Refer to the CData Prompt Library for examples of specific prompts.