1
Add the gateway
On the project’s Agents page, under Connect an agent, pick VS
Code and click Add to VS Code. VS Code opens and asks to install
midplane, in your user profile.Or add it by hand, for one workspace
Or add it by hand, for one workspace
In
.vscode/mcp.json, with the gateway’s URL from that card:2
Sign in
Start
midplane, and allow the sign-in.3
Choose what it may reach
Set each database to None, Read or Read + write, and Allow.
4
Try it
Ask Copilot, in agent mode, which tables it can see. Its statement shows
up in the project’s Query log.
You’re set: Copilot can answer questions from your data, and only what your
policy allows runs. Masked columns stay masked, writes that need approval
wait for a person, and every statement is in the audit log.
Permissions
VS Code asks before an MCP tool call, and lets you allow a tool for the session, the workspace or always. Of the gateway’s tools,query,
list_tables, describe_table and check_approval only read; write is
the one that changes data, and Midplane’s policy still decides whether it
runs, waits for an owner or admin, or is refused (what clients ask you to
confirm).
If it doesn’t work
- VS Code can’t connect to the URL: for a gateway at a Midplane URL, check that the setup step says Relay · connected, or the Gateways page Relay: connected, or see cannot reach the relay.
- The consent page says it wants access, with no databases: you aren’t a member of the gateway’s project, or the gateway isn’t registered. Ask an owner or admin of its organization to invite you.
- The
localhostURL does not resolve: see troubleshooting.
apps/gateway/test/auth.test.ts for the gateway’s side; the
client’s steps by hand.