Prisma MCP setup: workspace and Postgres databases
Start by checking the workspace and a database you already know.
Prisma MCP provides access to Prisma Postgres and Prisma documentation. Prepare a known database for your first check: its name, project and workspace should be easy to identify in your Console. This lets you distinguish a completed sign-in from a connection that actually reaches the intended resource.
Add the remote connection in VS Code
The documented HTTP endpoint is https://mcp.prisma.io/mcp. On first use, authenticate through Prisma Console and choose the intended workspace. Your VS Code project file, .vscode/mcp.json, can contain the following entry. Merge it into the existing server list if that file is already in use.
{
"servers": {
"prisma": {
"type": "http",
"url": "https://mcp.prisma.io/mcp"
}
}
}Start the server, complete browser sign-in and inspect the tools it exposes. The VS Code guide explains the client steps. This example connects to the hosted Prisma service; it does not establish that every local database file or arbitrary Postgres instance is accessible through that connection.
Begin with an inventory request
Read the workspace details and compare the selection with Prisma Console. In particular, check whether you are using a personal project or a shared one.
List existing Prisma Postgres databases. Compare the prepared database name and ID; do not create a new database just to obtain a successful response.
Ask a separate, specific documentation question, such as where to place a schema file. Open the linked vendor source and check that it applies to the version you use.
Record the workspace, database ID and comparison result. Repeat the test after restarting the client and verify which account is signed in.
Distinguish the types of tools
| Task | What to check |
|---|---|
| Inspect a workspace | fetch_workspace_details and the corresponding account selection. |
| List databases | list_prisma_postgres_databases and the expected project mapping. |
| Search documentation | search_prisma_documentation and the original linked sources. |
| Create a resource | Check write permissions, target project and required approval separately. |
Alongside read operations, the service exposes management actions. Selecting only read tools is not automatically the same as restricting the account’s permissions. Use the access planner before enabling more functionality. For requests against a particular database, the database planner also helps define the data scope and expected result.
Common questions
- Is this the same as starting a local Prisma CLI process?
- This guide sets up the hosted HTTP service. Older or differently structured examples using a local command describe another startup method and should be checked before reuse.
- Why is an expected database missing?
- Compare the account, workspace and project with Prisma Console. A similar name in another workspace does not confirm access to the intended resource.
- Can I connect any Postgres database this way?
- This guide covers the Prisma service and its documented tools. Another database requires a suitable connection with independently checked permissions and connection details.
- How should I verify a documentation answer?
- Open the original source and compare its version, example and prerequisites with your setup. Keep the source link together with your question so the answer can be checked later.
The Prisma registry search adds vendor declarations. Find related guides in the files and data app selection.
Vendor sources checked on 3 October 2026. The checks are intended for your own environment; no customer account was connected.
- Prisma: MCP configuration and tools
Show retrieval command
curl -s https://docs.prisma.io/docs/ai/tools/mcp-server - Prisma: service overview
Show retrieval command
curl -s https://www.prisma.io/mcp - VS Code: MCP configuration
Show retrieval command
curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers