Prisma CLI MCP

90/100
Last tested 2026-11-11 (Fresh: tested within 30 days) Working (tool call tested 2026-11-11) No key needed for the tools we called

No advisories in range for tested 7.10.1 (checked 2026-11-11)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs5/15
  • License10/10

Tested npm prisma 7.10.1 (Apache-2.0; repo prisma/orm packages/cli, 47,663 GitHub stars when checked) through `prisma mcp`, pinned: the npm latest tag, 8.0.0-rc.33, dropped the mcp command, so install and config here pin prisma@7.10.1. Stdio, 3 tools (migrate-status, migrate-dev, Prisma-Studio), no account for a local database. Real call: migrate-status on our local SQLite test database reported that the database is not managed by Prisma Migrate and no migrations exist, which is the correct status for that database (the tool relays the CLI's exit code 1 in its text; isError false). migrate-dev and Prisma-Studio change files or start a server and were not called. Not the hosted Prisma MCP (mcp.prisma.io), which needs a Prisma Console sign-in.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 1 of 1 read call passed on a local SQLite test database, no key. migrate-dev and Prisma-Studio not called. Evidence: local test run, Nov 11, 2026.

Transport (tested 2026-11-11): stdio

Token cost (estimate): approx. 495 tokens, cl100k estimate (3 tools, measured 2026-11-11, version 7.10.1). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 1 read, 1 write (state-changing), 1 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • Prisma-Studio — unclassified
  • migrate-dev — write (state-changing)
  • migrate-status — read

handshake and tools listed without a recorded key or OAuth

Score 90/100 · Tools 3 · Token cost approx. 495 tokens · Compare · Last tested 2026-11-11 · Version tested 7.10.1 · Package prisma · Repo prisma/orm

Summary: Prisma CLI MCP completed an MCP handshake without credentials and exposed 3 tools.

Evidence summary

Handshake
pass
Tools listed
3
Context cost
approx. 495 tokens, cl100k estimate (3 tools, measured 2026-11-11, version 7.10.1; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-11

Test results

TestResultPointsEvidence
installpass20npm install prisma (Node 20, Linux) succeeded in 6s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 3 tools listed in 0.5s.
maintenancepass25Repo pushed 0 days before test; 47,663 GitHub stars.
docspartial5README over 3,000 chars. Check of the package's own README (README shipped in npm package).
licensepass10Apache-2.0 (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 495 tokens, cl100k estimate for 3 tools · about 6% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-11

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 3 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-11 for version 7.10.1 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for prisma 7.10.1 as of 2026-11-11. This is not a security audit.

⚠ Newer version 8.0.0-rc.33 exists; not tested or checked here.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-11 test run; changes appear after the next test.

Note: tool list can depend on the connected database, so changes are annotated, not flagged automatically.

Snapshot hash (fingerprint of the tool list)

fbee70dbb510: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "prisma",
  "version": "7.10.1",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 3,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install prisma` (Node 20, Linux) succeeded in 6s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 3 tools listed in 0.5s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 47,663 GitHub stars."
    ],
    "docs": [
      "partial",
      5,
      "README over 3,000 chars. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "Apache-2.0 (OSI-approved)."
    ]
  }
}

Install

npx -y prisma@7.10.1 mcp

Pin the version we tested

npx -y prisma@7.10.1 mcp

tested 2026-11-11. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "prisma-cli-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prisma@7.10.1",
        "mcp"
      ]
    }
  }
}

Tools listed

Prisma-Studio, migrate-dev, migrate-status

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "prisma-cli-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prisma@7.10.1",
        "mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install prisma (Node 20). This is the exact command we ran on 2026-11-11.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (3 in our test).
{
  "mcpServers": {
    "prisma-cli-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prisma@7.10.1",
        "mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best database MCP servers · Troubleshooting: Unknown command or usage error

FAQ

Is Prisma CLI MCP deprecated?

No. prisma was not deprecated or archived when we last tested it on 2026-11-11.

What replaces Prisma CLI MCP?

Nothing; Prisma CLI MCP is not deprecated as of 2026-11-11.

Does Prisma CLI MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 3 tools.

Embed the badge

TestedMCP: 90/100, tested 2026-11-11

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue