MCP

Connect an AI agent to Subsalt over the Model Context Protocol to explore schemas, query synthetic data, and compute legally de-identified answers on real data.

Subsalt exposes a Model Context Protocol (MCP) server so AI agents — Claude, Cursor, and any other MCP-compatible client — can work with your data through a single authenticated connection. An agent connected to Subsalt can explore what data exists, iterate on fully synthetic data, and compute high-precision answers on real data that are legally de-identified before they ever reach the model.

The guiding principle is the same one behind the rest of Subsalt: neither the agent nor the user ever touches a sensitive row. The MCP server only ever returns metadata, synthetic data, or privacy-banded aggregates.

MCP is an open standard for connecting AI applications to external tools and data. If your client supports MCP, it can connect to Subsalt with no custom code — see connecting-a-client.md.

What an agent can do

The server groups its tools into three components, which together support the full analyst workflow:

Component	What it provides
Schema & metadata	The canonical description of what data exists — databases, tables, and columns with types, descriptions, sample values, and foreign keys. Safe to read; it describes structure, not sensitive values.
Synthetic data	Connection details for every database's representative synthetic data over a standard PostgreSQL interface — a fast, safe loop for exploring distributions and developing an analysis.
Secure Compute	A way to run an analysis script against real data inside an isolated environment and get back only privacy-banded aggregates — a precise answer that is legally de-identified under HIPAA.

For the complete tool list and the recommended workflow that ties these together, see tools-and-workflow.md.

How it fits with the rest of Subsalt

The MCP server is an alternative front door to the same platform described elsewhere in these docs. It authenticates with your normal Subsalt identity (including SSO), and every request it makes is authorized exactly as it would be through the portal or the PostgreSQL endpoint — an agent can only see the databases you can see.

• Prefer a SQL client or the portal for direct, interactive querying of synthetic data? See running-queries.md.

• Want an AI-assisted, natural-language path to a synthetic view without wiring up an agent? See data-request.md.

Getting started

1. Connect your MCP client to the Subsalt MCP endpoint and sign in.

2. Ask the agent to call the instructions tool first — it returns a getting-started guide and lists the databases available to you.

3. Explore, iterate on synthetic data, and confirm answers against real data with Secure Compute, following the standard workflow.