The governed MCP gateway for your data

Let your AI agents query your database — without handing over the keys.

TeamDuo turns your Postgres into a documented, governed MCP endpoint. Connect a database and your repo, and Claude, Cursor, or ChatGPT can run live analysis on real data — with permissions, masking, and a full audit log you control.

Connect your database →See how it works

Read-only by default · Your data never leaves your database · Free to start

teamduo — analytics-team workspace

1 · Connect & govern once

# connected sourcespostgres prod-db read-onlygithub /app-repo docs + schema# exposed to agentsresource mrr metric · verifiedresource active_usersresource orders (pii masked)deny customers.email, ssn
semantic layer · v14 ✓ reviewed

2 · Your agent queries live

You → Claude

What was our MRR last month vs the month before, by plan tier?

Claude · via TeamDuo

MRR rose 12.4% MoM to $148,200. Growth was led by the Team plan (+18%). Pulled from the verified mrr metric — no raw SQL, PII columns never touched.
✓ governed · logged · reproducible

Connect the agents your team already uses

Your sources

Start with Postgres. Bring the rest as you grow.

One governed gateway for every source your team connects — starting where your data already lives.

  • PostgreSQLAvailable
  • GitHub(schema & docs)Available
  • MySQLComing soon
  • SnowflakeComing soon
  • BigQueryComing soon
  • Google SheetsComing soon

Need something else? Request a source →

The problem

Handing an agent your database is a footgun

Point an AI agent at a raw connection string and you inherit three problems at once.

  • There's no access control in a SELECT

    A raw connection can read every column in every table — including PII you never meant an agent, or the vendor behind it, to see.

  • The same question returns different answers

    Agents re-invent joins, filters, and metric math every time. Ask for "revenue" twice and get two numbers. No one trusts the output.

  • You can't see what happened

    No record of which agent ran what, when, or what came back. Impossible to audit, debug, or hand to security.

How it works

From connection string to governed endpoint in minutes

TeamDuo sits between your data and any agent — the layer that understands, governs, and logs every request.

  1. Connect your data

    Add a Postgres connection (read-only by default). Point TeamDuo at your GitHub repo so it can read your schema and docs.

  2. Auto-document it

    TeamDuo drafts a semantic layer from your schema, migrations, and markdown — tables, columns, and metrics, described in plain language. You curate.

  3. Choose what's exposed

    Pick the resources agents can see. Mask columns, filter rows, and set who — which member, which agent — can reach what.

  4. Connect your agent

    Drop the TeamDuo MCP endpoint into Claude, Cursor, or ChatGPT. Your team runs live analysis and search — safely.

Features

More than a Postgres MCP server

The connection is the easy part. TeamDuo is the documentation, governance, and history around it.

  • Version-controlled semantic layer

    Every metric and definition is documented once, reviewed like code, and versioned — so answers are consistent and every change is traceable.

  • Auto-docs from DB + GitHub

    Bootstrap descriptions and business logic straight from your schema, migrations, and repo markdown. No blank-page documentation.

  • Column masking & row filters

    Expose a table without exposing PII. Rules are enforced at query time — an agent literally cannot request forbidden data.

  • Roles & per-agent permissions

    Admins control exposure; members consume. Scope access per person and per agent, and revoke it in one click.

  • Immutable audit log

    Every agent query — who, what, when, what returned — captured and exportable. Debuggable by you, defensible to security.

  • One endpoint, any agent

    A single governed MCP endpoint works across Claude, Cursor, ChatGPT, and VS Code. Postgres today; more sources coming.

The difference

Your data's meaning, under version control

Text-to-SQL gives an agent access to your data. A semantic layer gives it understanding. TeamDuo makes that understanding a reviewable, versioned artifact your team owns — not a prompt someone pasted once.

  • Define a metric once; every agent uses the same math.
  • Review changes to definitions and exposure before they go live.
  • Roll back instantly when a change breaks an answer.
  • Sync definitions to your Git repo, or keep them in TeamDuo.
semantic/metrics/mrr.yml+ reviewed by tony
metric: mrr
label: Monthly Recurring Revenue
- filter: status = 'active'
+ filter: status = 'active' AND is_trial = false
+ grain: month
access: [admin, analyst]
mask: [customer_email]
Why not a raw MCP server?

The gap that matters

CapabilityRaw DB MCP serverTeamDuo
Connect a databaseYesYes
Documented, consistent metricsNot supportedVerified & versioned
Column masking / row-level rulesNot supportedEnforced at query time
Team roles & per-agent accessNot supportedBuilt in
Audit log of every queryNot supportedImmutable & exportable
Change review & rollbackNot supportedGit-backed history
Security & trust

Built to be handed to your security team

  • Read-only by default

    Write access is opt-in and explicitly scoped. Safe is the default, not the config.

  • Your data stays put

    Queries run against your database. TeamDuo governs and logs access — it isn't a copy of your data.

  • Preview before you expose

    See exactly what an agent will see — masked columns and all — before anything goes live.

  • SSO & SOC 2 on the roadmap

    SAML/OAuth SSO and SOC 2 Type II for teams that need the paperwork.

Give your agents data they can trust.

Connect your first database in minutes. Free while you build — governance and team plans when you're ready.

Start free →Book a demo