Midplane

ai.midplanePublished by midplane.aiv0.26.1Updated Oct 30, 2026

A gateway between AI agents and Postgres: table access, masking at the source, approvals and audit.

Overview

AI-generated overview

Local MCP gateway that sits between AI agents and Postgres, granting table access with masking, approvals and an audit log.

What you can do
  • Give an assistant policy-checked access to Postgres tables you grant, with masked columns.
  • Hold agent writes for a person's approval before they run.
  • Parse, check and record every statement an agent sends before execution.
  • Contain agents once they read untrusted content.
  • Export and verify a hash-chained audit log kept on the gateway's disk.
When to use it
Use it when you want an AI assistant to query or modify Postgres data but need column masking, human approval for writes, and a verifiable audit trail. It suits teams that keep policy locally in a YAML file or centrally through Midplane Cloud.
Requirements
Runs locally over stdio via npx (Node 24.16 or newer) next to your databases. Needs a token from the midplane token command in MIDPLANE_TOKEN, ideally with a short TTL. Local mode uses a YAML policy file; linked mode needs Midplane Cloud and database connection strings entered during setup.
Before you install
The token in MIDPLANE_TOKEN stays in the entry, so give it a short TTL. Agents can write to your databases; writes are held for approval, but review the policy and grants carefully. Linked mode sends policy, identities, approvals and query logs through Midplane Cloud, and setup asks for database connection strings.

Installation

In SourceWeft

  1. Open Midplane in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

midplane

The Midplane gateway: an MCP server that sits between AI agents and your Postgres databases. Every statement an agent sends is parsed, checked against a policy and recorded before it runs. Agents get table access you grant, masked columns, writes held for a person's approval, and containment once they read untrusted content. It runs next to your databases; nothing connects in to it but agents.

sh
npx midplane --version

Node 24.16 or newer.

  • Local mode (midplane local): the policy lives in a YAML file and tokens come from midplane token. Try it with the quickstart.
  • Linked mode (midplane gateway): policy, identities, approvals and a query log come from Midplane Cloud, over a link the gateway opens. midplane setup makes one: it asks for each database's connection string, tests it, writes the gateway's folder, enrolls and starts it.
  • The audit log stays on the gateway's disk, hash-chained: midplane audit export and midplane audit verify.

Documentation: https://midplane.ai/docs. The image: ghcr.io/midplaneai/midplane. Both are signed: see verifying a release.

MIT licensed.

Source: apps/gateway/README.md at commit cd30f5e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.26.1LatestOct 29, 2026
  2. v0.20.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts