Mcp

The grounded data layer for any LLM: governed SQL, metrics, lineage and catalog over your data.

Mcp by Matih Labs is an MCP server published under the package @matihlabs/mcp (version 0.2.1) on npm. It is described as a grounded data layer for LLMs, covering governed SQL execution, metrics, data lineage, and a data catalog over your existing data infrastructure. The server communicates over stdio transport and requires a single environment variable, MATIH_MCP_TOKEN, for authentication. The repository is hosted at github.com/matih-labs/matih-mcp.

The core proposition is governance: rather than allowing an LLM to run arbitrary queries, this server sits as an intermediary that applies controls and structure — governed SQL, tracked lineage, defined metrics, and a browsable catalog. This makes it relevant for organizations that need auditability or policy enforcement around how AI agents interact with their data.

No tool definitions were provided in the registry record, so the specific callable operations exposed to an agent cannot be enumerated here. Developers evaluating this server should review the upstream repository to understand exactly what tools are available before integrating it into an agent workflow. The server requires Node.js tooling to install from npm and a valid MATIH_MCP_TOKEN credential to operate.

Use cases

  • Use it to give an LLM governed, policy-controlled access to SQL databases
  • Use it to expose a structured metrics layer to an AI agent rather than raw tables
  • Use it to surface data lineage information to an agent during analysis workflows
  • Use it to let an agent browse a governed data catalog for dataset discovery
  • Use it when auditability of LLM-driven data queries is a requirement

When to use it

  • When you need governance and policy enforcement over LLM SQL access
  • When data lineage tracking is required for AI-driven queries
  • When you want to expose a curated metrics layer rather than raw database access
  • When your project uses stdio transport for MCP communication

When not to use it

  • When you need a fully documented, enumerated tool list before integration — no tools are declared in the registry record
  • When your environment does not support stdio transport
  • When you do not have or cannot obtain a MATIH_MCP_TOKEN credential
  • When you need a server with a known open-source license — none is listed in the registry record