CData

CData Connect AI MCP Server

A hosted, remote Model Context Protocol server that exposes every data source connected to a CData Connect AI account as MCP tools — catalog, schema, table, column and stored procedure discovery plus SQL query and procedure execution. A companion Management MCP server at /mcp/mgmt lists available sources and creates, tests and manages connections. Both speak the MCP Streamable HTTP transport and authenticate with OAuth 2.1 (PKCE) or HTTP Basic with a Personal Access Token.

Documentation GitHub OpenAPI

Operations 2

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /mcp Send an MCP request across all my connections · Generic MCP Access #

Ask an LLM

“How do I talk to the CData Connect AI MCP server from my own model-aware client?”

“Can one MCP session reach every connection listed in my token instead of just one?”

Tell an agent

Send the MCP method {method} to the general MCP endpoint covering all my connections.

List MCP tools across all my connections, limited to tool types {tools}.

POST /mcp/connections/{connectionId} Send an MCP request scoped to one connection · Connection Scoped MCP Access #

Ask an LLM

“Can I restrict an MCP session to a single data connection?”

“How do I list only the MCP tools that belong to one specific connection?”

Tell an agent

Send MCP method {method} scoped only to connection {connectionId}.

List the MCP tools for connection {connectionId} limited to operations {ops}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/cdata:mcp"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Example Server MCP API
  version: 1.0.0
  description: This API provides a Model Context Protocol (MCP) server that exposes tools to connect your data with a model-aware client.
servers:
- url: https://mcp.cloud.cdata.com
  description: Production MCP base URL
security:
- BearerAuth: []
tags:
- name: MCP
paths:
  /mcp:
    post:
      summary: Generic MCP Access
      tags:
      - MCP
      description: 'Generic MCP endpoint. Implements the

        MCP Streamable HTTP transport.

        Send any JSON-RPC 2.0 MCP request (for example, `initialize`, `tools/list`, `tools/call`) in the

        request body. The session can access any connection whose ID is listed in the JWT''s

        `connection_ids` claim.


        Use `/mcp/connections/{connectionId}` instead to scope a session to a single connection.


        Omit `id` to send a notification (fire-and-forget; the server returns `202 No Content`).'
      parameters:
      - name: tools
        in: query
        required: false
        style: form
        explode: false
        description: 'Comma-separated list of tool types to include in `tools/list` responses. Omitting returns all types. If repeated, only the first occurrence is used. An empty string or unrecognized value returns `HTTP 400`. Narrowing-only: cannot enable tools the server has already disabled.

          '
        schema:
          type: array
          items:
            type: string
            enum:
            - universal
            - sql
            - source
      - name: ops
        in: query
        required: false
        style: form
        explode: false
        description: 'Comma-separated list of operation base names to include in `tools/list` responses. Omitting returns tools for all operations. If repeated, only the first occurrence is used. An empty string or unrecognized value returns `HTTP 400`. Narrowing-only: cannot enable tools the server has already disabled.

          '
        schema:
          type: array
          items:
            type: string
            enum:
            - get_catalogs
            - get_schemas
            - get_tables
            - get_columns
            - get_procedures
            - get_procedure_parameters
            - get_instructions
            - execute_sql
            - execute_select
            - execute_insert
            - execute_update
            - execute_procedure
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/JsonRpcRequest'
            examples:
              initialize:
                summary: Initialize the MCP session
                value:
                  jsonrpc: '2.0'
                  method: initialize
                  params:
                    protocolVersion: '2024-11-05'
                    capabilities: {}
                    clientInfo:
                      name: my-client
                      version: 1.0.0
                  id: 1
              tools_list:
                summary: List available tools
                value:
                  jsonrpc: '2.0'
                  method: tools/list
                  params: {}
                  id: 2
              tools_call:
                summary: Invoke a tool
                value:
                  jsonrpc: '2.0'
                  method: tools/call
                  params:
                    name: GetTables
                    arguments: {}
                  id: 3
      responses:
        '200':
          description: "JSON-RPC response or SSE stream, depending on the request.\n\n- **`application/json`** — returned for a single request that includes an `id`.\n  The body is a `JsonRpcResponse` object.\n- **`text/event-stream`** — returned when the server needs to stream multiple\n  messages back (for example, long-running tool calls, server-initiated notifications).\n  Each SSE `data:` line is a JSON-encoded `JsonRpcResponse` object. The stream\n  closes when the server has sent all messages for the request.\n"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JsonRpcResponse'
              example:
                jsonrpc: '2.0'
                result:
                  tools:
                  - name: GetTables
                    description: Returns a list of available tables.
                    inputSchema:
                      type: object
                      properties: {}
                id: 2
            text/event-stream:
              schema:
                type: string
                description: 'Newline-delimited SSE events. Each `data:` field contains a

                  JSON-encoded `JsonRpcResponse`. Example:


                  ```

                  data: {"jsonrpc":"2.0","result":{...},"id":3}


                  data: {"jsonrpc":"2.0","method":"notifications/message","params":{...}}


                  ```

                  '
        '202':
          description: Notification accepted (request had no `id`); no response body.
        '400':
          description: 'Bad request. Returned for either of:

            - Request body is malformed JSON or is not a valid JSON-RPC 2.0 envelope.

            - A `tools` or `ops` query parameter is empty or contains an unrecognized value (`ToolFilterParseError`, JSON-RPC code `-32602`).

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ToolFilterParseError'
        '401':
          description: Missing or invalid bearer token.
      operationId: postMcp
      x-operation-id-source: derived
  /mcp/connections/{connectionId}:
    post:
      summary: Connection Scoped MCP Access
      tags:
      - MCP
      description: ''
      parameters:
      - name: connectionId
        in: path
        required: true
        schema:
          type: string
          format: uuid
        description: The unique identifier of the connection to scope this request to.
      - name: tools
        in: query
        required: false
        style: form
        explode: false
        description: 'Comma-separated list of tool types to include in `tools/list` responses. Omitting returns all types. If repeated, only the first occurrence is used. An empty string or unrecognized value returns `HTTP 400`. Narrowing-only: cannot enable tools the server has already disabled.

          '
        schema:
          type: array
          items:
            type: string
            enum:
            - universal
            - sql
            - source
      - name: ops
        in: query
        required: false
        style: form
        explode: false
        description: 'Comma-separated list of operation base names to include in `tools/list` responses. Omitting returns tools for all operations. If repeated, only the first occurrence is used. An empty string or unrecognized value returns `HTTP 400`. Narrowing-only: cannot enable tools the server has already disabled.

          '
        schema:
          type: array
          items:
            type: string
            enum:
            - get_catalogs
            - get_schemas
            - get_tables
            - get_columns
            - get_procedures
            - get_procedure_parameters
            - get_instructions
            - execute_sql
            - execute_select
            - execute_insert
            - execute_update
            - execute_procedure
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/JsonRpcRequest'
            examples:
              initialize:
                summary: Initialize the MCP session
                value:
                  jsonrpc: '2.0'
                  method: initialize
                  params:
                    protocolVersion: '2024-11-05'
                    capabilities: {}
                    clientInfo:
                      name: my-client
                      version: 1.0.0
                  id: 1
              tools_list:
                summary: List available tools
                value:
                  jsonrpc: '2.0'
                  method: tools/list
                  params: {}
                  id: 2
              tools_call:
                summary: Invoke a tool
                value:
                  jsonrpc: '2.0'
                  method: tools/call
                  params:
                    name: GetTables
                    arguments: {}
                  id: 3
      responses:
        '200':
          description: "JSON-RPC response or SSE stream, depending on the request.\n\n- **`application/json`** — returned for a single request that includes an `id`.\n  The body is a `JsonRpcResponse` object.\n- **`text/event-stream`** — returned when the server needs to stream multiple\n  messages back (for example, long-running tool calls, server-initiated notifications).\n  Each SSE `data:` line is a JSON-encoded `JsonRpcResponse` object. The stream\n  closes when the server has sent all messages for the request.\n"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JsonRpcResponse'
              example:
                jsonrpc: '2.0'
                result:
                  tools:
                  - name: GetTables
                    description: Returns a list of available tables.
                    inputSchema:
                      type: object
                      properties: {}
                id: 2
            text/event-stream:
              schema:
                type: string
                description: 'Newline-delimited SSE events. Each `data:` field contains a

                  JSON-encoded `JsonRpcResponse`. Example:


                  ```

                  data: {"jsonrpc":"2.0","result":{...},"id":3}


                  data: {"jsonrpc":"2.0","method":"notifications/message","params":{...}}


                  ```

                  '
        '202':
          description: Notification accepted (request had no `id`); no response body.
        '400':
          description: 'Bad request. Returned for any of:

            - `connectionId` path parameter is not a valid UUID.

            - Request body is malformed JSON or is not a valid JSON-RPC 2.0 envelope.

            - A `tools` or `ops` query parameter is empty or contains an unrecognized value (`ToolFilterParseError`, JSON-RPC code `-32602`).

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ToolFilterParseError'
        '401':
          description: Missing or invalid bearer token.
        '403':
          description: 'Forbidden. The authenticated token''s allowed `connection_ids` list does not

            include the requested `connectionId`.

            '
        '404':
          description: Connection ID not found.
      operationId: postMcpConnectionsByConnectionId
      x-operation-id-source: derived
components:
  schemas:
    JsonRpcResponse:
      type: object
      required:
      - jsonrpc
      - id
      properties:
        jsonrpc:
          type: string
          enum:
          - '2.0'
          description: JSON-RPC protocol version.
        result:
          type: object
          additionalProperties: true
          description: Present on success; mutually exclusive with `error`.
        error:
          $ref: '#/components/schemas/JsonRpcError'
        id:
          description: Matches the `id` from the request. Null if the server could not determine the request id.
          oneOf:
          - type: string
          - type: integer
    ToolFilterParseError:
      type: object
      description: Returned when a `tools` or `ops` query parameter is empty or contains an unrecognized value.
      properties:
        jsonrpc:
          type: string
          enum:
          - '2.0'
        error:
          type: object
          properties:
            code:
              type: integer
              description: JSON-RPC error code indicating invalid parameters.
              example: -32602
            message:
              type: string
              description: Human-readable description of the parse failure.
              example: 'Invalid value for parameter ''tools'': ''unknown'''
        id:
          oneOf:
          - type: string
          - type: integer
    JsonRpcRequest:
      type: object
      required:
      - jsonrpc
      - method
      properties:
        jsonrpc:
          type: string
          enum:
          - '2.0'
          description: JSON-RPC protocol version. Must be `"2.0"`.
        method:
          type: string
          description: MCP method name (for example, `initialize`, `tools/list`, `tools/call`).
        params:
          type: object
          additionalProperties: true
          description: Method-specific parameters. May be omitted for parameterless methods.
        id:
          description: 'Request identifier echoed in the response. Use a string or integer.

            Omit entirely to send a notification (no response will be returned).

            '
          oneOf:
          - type: string
          - type: integer
    JsonRpcError:
      type: object
      required:
      - code
      - message
      properties:
        code:
          type: integer
          description: JSON-RPC error code (for example, `-32600` invalid request, `-32601` method not found, `32602` tool filter parse error).
        message:
          type: string
          description: Human-readable error description.
        data:
          description: Optional additional error context.
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT token authentication. Include the token in the Authorization header as 'Bearer <token>'.

CData Connect AI MCP Server

Operations 2

Documentation

Specifications

Schemas & Data

Other Resources