Agent MCP Directory

Prisma: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Prisma at mcp.prisma.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyPrisma
Domainprisma.io
CategoryDeveloper Tools (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Ora score82, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for prisma.io, a vendor-published score)
Company found throughthe vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.prisma.io/mcp
How it was foundlisted in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:04 UTC
Handshake time1,446 ms over 1 attempt
Documentationwww.prisma.io

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:58:59Z https://mcp.prisma.io/mcp sent initialize result auth-required (HTTP 401) 1562 ms
  • 20:04:06Z https://mcp.prisma.io/mcp sent initialize result auth-required (HTTP 401) 1446 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.prisma.io/.well-known/oauth-protected-resource/mcp"
Protected resource metadatamcp.prisma.io
Authorization server metadataauth.prisma.io
Registration endpointhttps://auth.prisma.io/register
Auth as listed by a registryOAuth2.1 (a claim, not checked by connecting)

The sign-in route, step by step

  1. Request https://mcp.prisma.io/mcp without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.prisma.io/.well-known/oauth-protected-resource/mcp to find the authorization server.
  3. Register a client at the registration endpoint https://auth.prisma.io/register (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

Packageprisma on npm (page)
Existsyes
Latest version8.0.0-rc.30
Last publish3 November 2026
Command namesprisma
Checked4 November 2026

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileFound: www.prisma.io (JSON, via a direct request).
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileFound: prisma.io/.well-known/mcp.json answered with a valid document in the shared crawl.
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversYes
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.