Connect Claude Code, Cursor, or VS Code to your database schema

Connecting an AI coding agent to your database schema takes one URL and a browser sign-in. There is no key to generate, nothing to install beside the agent you already use, and no connection to your database: the agent reads and edits the design, a set of schema documents and their ER diagram in DB Planner.

The URL is the same for every client:

MCP server
https://api.dbplanner.io/mcp

What differs is where each client wants it. The steps below were checked against each client’s own documentation in November 2026. If a menu has moved since, look for “MCP servers” or “connectors” in its settings and add a remote HTTP server with that URL.

Claude Code

One command in a terminal:

terminal
claude mcp add --transport http db-planner https://api.dbplanner.io/mcp

To share the server with everyone who works in a repository, commit it as a .mcp.json at the repository root instead:

.mcp.json
{
  "mcpServers": {
    "db-planner": {
      "type": "http",
      "url": "https://api.dbplanner.io/mcp"
    }
  }
}

That file holds a URL and nothing secret, so it is safe to commit. Each person still signs in as themselves the first time their agent uses it.

Cursor

Cursor reads MCP servers from .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project on your machine. A remote server is just its URL:

.cursor/mcp.json
{
  "mcpServers": {
    "db-planner": {
      "url": "https://api.dbplanner.io/mcp"
    }
  }
}

Claude on the web and Claude Desktop

  1. Open Customize, then Connectors.
  2. Choose Add, then Add custom connector.
  3. Name it “DB Planner”, paste the URL, and continue.
  4. Sign in to DB Planner when asked, and choose what the connector may do.

On a Team or Enterprise plan an owner adds the connector for the organization, and each member then connects their own DB Planner account to it.

VS Code

  1. Open the Command Palette and run MCP: Add Server.
  2. Choose HTTP and paste the URL.
  3. Give it the id db-planner and choose whether it applies to this workspace or to all of them.

Any other MCP client

The server speaks the standard streamable HTTP transport and describes its own sign-in through the usual discovery documents, so a client needs only the URL. If yours asks for a transport, it is HTTP. If it asks for an API key, it does not yet support signing in to remote servers, and will not work until it does.

What happens the first time

The first time the agent reaches for a DB Planner tool, a browser window opens. You sign in to DB Planner (or create a free account), and a consent screen shows what the client is asking for:

  • Read is always granted. It lets the agent see your organizations, projects, documents, and boards.
  • Write is a switch, on by default. Turn it off and every tool that changes something is refused by the server, whatever the agent tries.

For a first session, turning write off costs you nothing and tells you a lot: see how to let an AI agent design your database for the method. Reading is part of the free plan; an agent making edits is part of Pro.

No password or API key is stored in the client. It holds a token that it refreshes on its own, so you sign in once per client.

Check that it worked

Ask the agent something only the connection can answer:

prompt
Which DB Planner account am I connected as, and which projects can you see?

It should name your account and list your projects. The agent sees exactly what your account can see, with the role you hold in each project, and nothing of anyone else’s.

When it does not work

What you seeWhat it means
No browser window opensThe client has not been restarted since the server was added, or it has not called a tool yet. Restart it and ask the check question above. In Claude Code, /mcp lists the server and starts the sign-in.
The agent can read but every edit is refusedThe connection was approved without write access, or the account is on the free plan. Disconnect and sign in again with write on, or start the Pro trial.
A project is missingYou are signed in as an account that is not a member of it. Ask the agent which account it is connected as.
The client asks for an API keyThere is none. That client does not support browser sign-in for remote servers.

What to do next

With the agent connected, start by having it explain a schema back to you. The prompt library has openers for understanding, designing, and reviewing. If its main job is writing application code, give it a standing rule to read the schema first: why your coding agent guesses your schema has one to copy.