Data Access (MCP)

MCP server that exposes workspace data through SQL query tools for use with Claude Desktop, Claude Code, and other MCP clients.

The Data-MCP service is a Model Context Protocol (MCP) server that gives MCP-compatible clients direct query access to workspace data. If you use Claude Desktop, Claude Code, or any other MCP client, you can connect it to your workspace and run SQL queries, inspect schemas, and profile data without building custom integrations.

How It Works

Data-MCP exposes workspace data through a set of SQL-based tools. Clients connect over stateless HTTP transport - no session affinity or sticky connections required. The server works behind load balancers without special configuration.

Authentication uses a standard Bearer token in the Authorization header plus an X-Workspace-Id header to scope queries. Every query runs within the boundaries of the authenticated workspace. There is no cross-workspace data access.

Available Tools

Data-MCP provides seven tools:

Tool	What It Does
sql_query	Run a SELECT query against workspace data. Results are limited to 1,000 rows with a 30-second timeout. Write operations are not permitted.
describe_query	Analyze a query and return the result schema (column names and types) without executing it. Useful for validating queries before running them.
tables	List available tables in the workspace. Supports filtering by name pattern.
table_schema	Return column names and data types for a specific table.
sample_data	Preview rows from a table without writing a full query.
table_detail	Extended metadata for a table including row counts, storage statistics, and partitioning information.
profile_column	Statistical profile of a single column: min, max, null count, distinct count, and value distribution.

Workspace Isolation

All queries are scoped to the authenticated workspace. The MCP server enforces this at the query layer - there is no way for a client to access data from another workspace, even with a valid API key. This follows the same isolation model described in Workspaces.

Connecting an MCP Client

Point your MCP client at the Data-MCP server endpoint with your API key and workspace ID. The server uses standard HTTP transport, so any client that supports the Model Context Protocol can connect without custom adapters or plugins.

Data-MCP only supports read operations. All queries are SELECT-only. If you need to write data, use the Platform API's data source endpoints or the connector runner's inbound pipeline.