> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/data/data-mcp.md).

# Data Access (MCP)

Standalone MCP service for read-only SQL exploration using Classic API organization credentials.

{% hint style="info" %}
**Choose the surface that matches the caller.** Use [platform functions](/agent/platform-functions.md) when an agent needs data during a conversation. For external clients using Platform API workspace credentials, use the [Platform API MCP server](https://docs.concurrence.com/developer-guide/platform-api/functions/mcp-server). This page describes Data-MCP, a separate service for integrations that use Classic API organization credentials.
{% endhint %}

Data-MCP is an active, standalone Model Context Protocol service for exploring data through read-only SQL tools. It uses MCP Streamable HTTP and can be used by compatible MCP clients.

## Scope and Authentication

Data-MCP uses the Classic API organization model. A connection supplies an organization ID plus either a pre-exchanged bearer token or the complete Classic API key credential set. Queries run through the Classic API under that organization and credential context.

This contract is different from the Platform API MCP server, which uses Platform API credentials and an explicit workspace ID. Do not send a Platform API workspace header to Data-MCP or assume that credentials can be exchanged between the two services.

Data-MCP is not scoped to an individual end user inside an application. When clinicians or other external users require role-specific access, use an [external-principal](/operations-and-safety/compliance.md#external-principals) agent session or another application authorization layer rather than sharing a broad MCP credential.

## Available Tools

Data-MCP exposes seven tools:

| Tool                | What It Does                                                                                            |
| ------------------- | ------------------------------------------------------------------------------------------------------- |
| **sql\_query**      | Run a read-only SQL query. Results are limited to 1,000 rows and the query has a 30-second timeout.     |
| **describe\_query** | Return the output columns and types a query would produce without running the query itself.             |
| **tables**          | List accessible tables, optionally filtered by a name pattern.                                          |
| **table\_schema**   | Return columns, types, and available descriptions for a table.                                          |
| **sample\_data**    | Preview a bounded number of rows from a table.                                                          |
| **table\_detail**   | Return available table statistics, properties, partitioning, and freshness metadata.                    |
| **profile\_column** | Summarize a column's cardinality, null rate, value range, and distribution where supported by its type. |

The service also exposes a data-catalog resource that helps clients discover table definitions and query guidance.

## Read-Only Boundary

The SQL execution tool accepts read-only `SELECT` queries. It is intended for exploration and analysis, not for creating tables or changing application data. Use the appropriate Platform API write endpoint, platform function, or configured integration for mutations.

Tool output reflects the tables visible to the supplied Classic API credential and the freshness of the underlying analytical data. A successful query is not evidence that every source system is current or that the result is appropriate for a particular end user.

## Regional Use

Data-MCP has regional deployments. Use the deployment and Classic API backend that correspond to the organization whose data you are querying. The service can accept an allowlisted backend override, so endpoint selection remains part of the client's residency configuration rather than an automatic global-routing guarantee.

For connection headers, endpoint URLs, and examples, see the [Data-MCP developer guide](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/data-mcp).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/data/data-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.