The Catalogue in Your IDE: Native MCP Server
Your IDE queries the catalogue without leaving the editor — and without bypassing a single permission.
Framework / standard: MCP spec · authz server-side
Your developers live in their IDE and their AI assistant; the catalogue lives in another tab that almost nobody opens. Linedat is a native MCP provider: the catalogue is exposed directly to Claude, Cursor or Claude Desktop.
52 tools, authz on the server
The MCP server exposes 52 catalogue tools (read and write). An engineer asks "which columns feed revenue_daily?" from their assistant and the answer comes from Linedat, with authorisation applied on the server (PAT per tenant), without bypassing a single permission or quota.
A thin facade over REST
The MCP is a thin facade over the REST API: it does not implement business logic or duplicate authorisation. The backend is the single source of truth for permissions, quotas and consent.
The limits (what we do not claim)
The current transport is stdio with a PAT bound to one tenant; full multi-user support via HTTP is a later phase. The MCP does not bypass Permission, QuotaGuard or the consent gate — precisely because it does not re-implement that logic.
How Linedat helps
Linedat puts governance in the engineer's workflow: the catalogue inside Claude or Cursor, with authorisation applied on the server. A real differentiator in 2026.
Related capabilities
Find your "churn tables" even if none of them are called that — and with an audit trail.
3-Level RBAC with Separation of DutiesThe person who operates the data is not the person who governs it. By design.
Impact Analysis Before Breaking AnythingBefore dropping a column, you see the 14 dashboards and 3 models that will break.