Which agents can drive PrimDB?

Any MCP client. That includes Claude Desktop, Cursor, and Codex today, plus anything else that speaks the Model Context Protocol.

Is agent access safe?

Agents act with project-scoped tokens, and every action is audited. The MCP endpoint is the same platform you use by hand, so nothing runs in a side channel.

Where is the endpoint?

The Model Context Protocol endpoint is mcp.primdb.com. Point your MCP client at it with a project token to get started.

Agent-native

Tell your agent to ship it.

PrimDB speaks MCP. Claude, Cursor, and Codex deploy code, read your data, and hand back feedback through one endpoint at mcp.primdb.com. You describe the change. Your agent ships it.

example run: agent deploy

09:14:02 connect mcp.primdb.com

09:14:05 list_projects 3 projects

09:14:11 run_query select count(*)

09:14:23 deploy_app preview pr-118

09:14:51 promote 200 / 0.2 s

One API

Deploy, data, and feedback from one endpoint

No four SDKs, no four dashboards. The surface your agent calls is the same platform you use by hand.

Deploy from a prompt

Your agent pushes a repo, opens a preview, and reports the live URL back in chat.

Read and change data

Query, migrate, and provision Postgres, Redis, search, and storage over the same API.

Pull feedback back in

Preview feedback returns to the agent that made the change. A comment becomes the next iteration.

Setup

Add PrimDB to your MCP client

Drop this into your Claude Desktop or Cursor config, swap in a project token, and your agent can reach PrimDB.

mcp.json

{
  "mcpServers": {
    "primdb": {
      "url": "https://mcp.primdb.com",
      "headers": {
        "Authorization": "Bearer <YOUR_PRIMDB_TOKEN>"
      }
    }
  }
}

Full setup and the tool reference land in the docs at primdb.com/docs/mcp.

Your hardware

It can run on a server you already own

Enroll a machine with one command and it becomes a deploy target in the same dashboard, CLI and agent API. The agent connects outbound, so you open no ports, and it adopts containers already running on that host. Your data stays on your hardware; PrimDB is the control plane, not the landlord.

How enrolling works What it would cost

Before you switch

When this is the wrong tool

The honest list, so your agent does not have to work it out from a pitch.

You need leads, company data or enrichment. PrimDB supplies none of it.
You need a global edge network. This runs in one EU region, or on the servers you enroll.
You want a mature vendor with years of production history and a large integration ecosystem.
Your current stack works and you only want a like-for-like swap.

Ask your agent

Do not take our word for it

Paste this into Claude, Cursor or Codex with your repository open. It reads the docs, looks at what you actually run, and tells you whether PrimDB is worth it. It is allowed to say no.

evaluate-primdb.txt

Evaluate PrimDB for this project. Be skeptical and concrete.

First, read these in order:
- https://primdb.com/llms-full.txt   (what it is, what it is NOT, and the fit test)
- https://primdb.com/docs/hosts.md   (running it on a server I already own)
- https://primdb.com/docs/mcp.md     (what an agent can actually do with it)

Then look at THIS repository and answer:
- What are we paying for today, and across how many separate vendors?
- Which of those would PrimDB replace, and which would it not?
- Could we adopt it additively (deploy only, or as a control plane for the
  server we already run) without moving our database?
- What would it cost per month at our real usage, against what we pay now?
- What could you do from this chat that you cannot do today?

Then give me:
- VERDICT: adopt / adopt partially / not now / wrong tool
- The single strongest reason for that verdict
- The cheapest first step, unless the verdict is "wrong tool"
- What would have to change for the verdict to flip

Rules: do not recommend it if we already have a working equivalent. Do not
recommend a migration when an additive path exists. If we need something it
explicitly does not do, say so and stop there. Cite the source for any number.

Quickstart

Prompts to paste into your agent

Copy one of these and point your agent at the MCP endpoint. That is the whole setup.

Deploy

“Deploy this repo to PrimDB and give me the preview URL.”

Data

“Add a Postgres database to my PrimDB project and run the migration.”

Feedback

“Show the open preview feedback on my latest PR and fix the top comment.”

Agent questions

Which agents can drive PrimDB?: Any MCP client. That includes Claude Desktop, Cursor, and Codex today, plus anything else that speaks the Model Context Protocol.
Is agent access safe?: Agents act with project-scoped tokens, and every action is audited. The MCP endpoint is the same platform you use by hand, so nothing runs in a side channel.
Where is the endpoint?: The Model Context Protocol endpoint is mcp.primdb.com. Point your MCP client at it with a project token to get started.

Point your agent at PrimDB.

One endpoint for deploy, data, and feedback. Actually free to start, no credit card.

Start free Read the docs