> ## 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.

# MCP

> Connect AI supports connectivity to the Model Context Protocol (MCP), the open-source standard for connecting AI applications to external systems. It was developed by Anthropic to bridge the gap between structured data and large language models (LLMs). MCP can be used from any client integration that supports it, such as [Claude](/en/Clients/Claude-Client), [Microsoft Copilot Studio](/en/Clients/MicrosoftCopilot-Client), and [n8n](/en/Clients/N8N-Client). See [AI Tools](/en/Clients/AITools) for a complete list of AI integrations.

To use MCP from a supported client tool, add the following URL to the **Remote MCP Server URL field**: *[https://mcp.cloud.cdata.com/mcp](https://mcp.cloud.cdata.com/mcp)*. Once you are connected to the MCP server, you can ask natural-language questions about your data.

<Tip>
  New to MCP with Connect AI? [Quick Start](/en/Quick-Start-Guide) walks through
  connecting an agent and running a query in about five minutes, using a public sample file so that no
  credentials of your own are required.
</Tip>

## Authentication

Authentication to MCP depends on the client integration tool. Connect AI supports both OAuth and Basic Authentication. Basic Authentication requires the Connect AI User Id and the PAT generated on the Connect AI [Personal Access Tokens](/en/Settings/Personal-Access-Tokens) page.

See [Authentication](/en/API/Authentication) for more details.

## MCP Tools

LLMs depend on the use of data resources to return data. The Connect AI MCP Server uses the following tools to provide data in response to natural-language questions:

* **getCatalogs**—retrieves a list of available connections from Connect AI.
* **getSchemas**—retrieves database schemas from Connect AI for a specific catalog. Schemas organize tables and stored procedures within a catalog.
* **getTables**—retrieves database tables from Connect AI for a specific catalog and schema.
* **getColumns**—retrieves a list of available database columns from Connect AI for a specific catalog, schema, and table. This resource examines the table structure and column definitions.
* **getInstructions**—retrieves connector-specific guidance and best practices for a data source, including syntax requirements, data type mappings, and known limitations.
* **getProcedures**—retrieves stored procedures from Connect AI for a specific catalog and schema. Stored procedures contain executable SQL logic within a schema.
* **getProcedureParameters**—retrieves parameter metadata for stored procedures from Connect AI for a specific catalog, schema, and procedure. Parameter metadata includes names, data types, and directions required for proper procedure execution.
* **executeProcedure**—executes the stored procedure for the chosen catalog and schema.
* **queryData**—executes SQL queries against the connected data sources and retrieves results.
* **execute\_insert**—inserts rows into a table. The **queryData** tool accepts only SELECT statements, so writes use this tool instead.
* **execute\_update**—updates existing rows in a table.

<Note>
  Queries through **queryData** must use fully qualified table names in the form
  *\[Catalog].\[Schema].\[Table]*. Brackets are required around names that contain characters such as
  hyphens. Results are returned in CSV format.
</Note>

## Limit What an Agent Can Do

Append the `ops` query parameter to the server URL to narrow the tools the server advertises in its
`tools/list` response. The parameter is narrowing-only: it cannot enable a tool that the server has
already turned off.

Accepted values:

| Value | Tool it controls |
| :- | :- |
| `get_catalogs` | getCatalogs |
| `get_schemas` | getSchemas |
| `get_tables` | getTables |
| `get_columns` | getColumns |
| `get_instructions` | getInstructions |
| `get_procedures` | getProcedures |
| `get_procedure_parameters` | getProcedureParameters |
| `execute_procedure` | executeProcedure |
| `queryData` | queryData, which reads data |
| `execute_insert` | execute\_insert, which adds rows |
| `execute_update` | execute\_update, which changes rows |
| `execute_sql` | Deprecated alias for `queryData` |

To give an agent read-only access, list the metadata operations and `queryData`, and leave out the
three that write:

```text wrap theme={null}
https://mcp.cloud.cdata.com/mcp?ops=get_catalogs,get_schemas,get_tables,get_columns,get_instructions,queryData
```

The server then advertises six tools instead of eleven: `getCatalogs`, `getSchemas`, `getTables`,
`getColumns`, `getInstructions`, and `queryData`.

An empty or unrecognized value returns `HTTP 400` with the JSON-RPC error code `-32602`. The error
message lists every accepted value, so a typo tells you what to use instead.

<Warning>
  Do not use the `tools` query parameter to restrict an agent. Although it accepts `universal`, `sql`,
  and `source`, it does not narrow the tool list. `universal` returns every tool, and `sql` and
  `source` cause `tools/list` to fail with `-32601 Method not found`. Use `ops` instead.
</Warning>

<Note>
  For durable, named restrictions that you manage in the interface rather than in a URL, use
  [Toolkits](/en/Toolkits), which expose only the tables and operations you select.
</Note>

## Verify the Server Responds

To confirm that the MCP server is reachable and to list the tools available to your account, send a
`tools/list` request. This works before any client is configured, which separates a Connect AI problem
from a client configuration problem. Create a personal access token on the
[Personal Access Tokens](/en/Settings/Personal-Access-Tokens) page, then run the following command:

```bash wrap theme={null}
curl -X POST https://mcp.cloud.cdata.com/mcp \
  -u "<YOUR_EMAIL>:<YOUR_PAT>" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
```

The response is a JSON-RPC result containing an entry for each tool listed above. If the request
returns an authentication error, confirm that the token has not expired on the **Security** tab of
**Settings**.

## 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](https://www.cdata.com/solutions/mcp/prompt-library/) for examples of specific prompts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.