Where can I host a TypeScript MCP server with Postgres?
A database-backed MCP server might expose tools such as looking up an order or creating a support ticket. It is an application with an API and authorization rules. The fact that an AI client calls the tools does not change who is allowed to read or modify the underlying records.
We make Prisma Compute and Prisma Postgres. The official documentation linked here was checked on October 27, 2026. This guide concerns hosting your own tools; the Prisma provider MCP guide covers an assistant managing platform resources.
What does the server need from its host?
Choose the transport before choosing the deployment. The MCP specification distinguishes a client-launched stdio process from a remote Streamable HTTP endpoint. Use a current SDK and a protocol version that your actual client supports; do not assume an older example's handshake or session behavior applies to every version.
The host must support the server's runtime, request handling and response streaming. The application also needs server-side secrets, a database connection, readable logs and a way to deploy the same configuration to a separate test environment. Persist tickets and tool execution records in the database, rather than assuming a process or local file survives a restart.
An HTTP transport does not authorize a tool. Authenticate the caller and bind their account or tenant on the server before invoking a database query. A prompt saying "only use your own records" is not an access check.
Which hosting setup fits?
These options are ordered alphabetically by app host. The database can remain Prisma Postgres in each setup.
| App host | Useful fit | What to verify |
|---|---|---|
| Prisma Compute | You want a TypeScript HTTP service and its Postgres dependency declared in one project. | Runs on Bun, without WebSocket servers or a persistent writable filesystem. |
| Render | You want a separate conventional web service with your existing server start command. | Configure its server-side database connection and deployed region. |
| Vercel | Your MCP endpoint belongs in a supported web app, including one using its documented MCP handler. | Test the handler, authentication and execution limits on the deployed endpoint. |
Prisma Compute's integration is useful when a coding assistant should be able to inspect the service's database dependency alongside its build and deployment configuration. Prisma ORM is optional; a plain database dependency can supply the connection for the client you already use.
How do I set up the Prisma path?
1. Deploy an HTTP service rather than a local-only process
Follow Composer getting started or porting an existing app. Use an MCP SDK HTTP transport compatible with your framework. Test the service under Bun before choosing Prisma Compute, including its request and response streaming behavior.
Keep the tool implementations separate from the HTTP adapter so they can be exercised without a public deployment. Configure the endpoint's authentication and allowed origins using the MCP security guidance. For browsers and cross-origin clients, verify the actual headers required by the chosen protocol and client; a health page returning 200 does not test MCP communication.
2. Give the service its own database dependency
Follow the Composer database guide to declare a plain Postgres resource that provisions a database and supplies connection configuration; your server creates the client and your team manages migrations. A separately provisioned database is another path, with its URL supplied through the server's environment. Do not create both and assume they refer to the same resource.
While developing with fictional data, define how the schema records the resource a tool changes, the user or account it belongs to and a durable request identifier when repeated calls can create duplicate work. Use parameterized queries, validate tool inputs and obtain identity from verified authentication rather than a tool argument supplied by the client.
3. Verify rejection before testing a successful tool call
Set MCP_URL to your test service's MCP endpoint. This negative probe deliberately omits credentials; run it only against that test endpoint.
curl --silent --show-error --output /dev/null --write-out '%{http_code}\n' \
--request POST "$MCP_URL" \
--header 'Content-Type: application/json' \
--data '{}'For a service configured to reject unauthenticated requests before processing tool messages, the result should be 401. A different result needs investigation against the chosen authentication design. This probe tests rejection only; it does not prove the endpoint speaks MCP correctly.
Then connect the actual authenticated client using the SDK's HTTP client workflow. List tools and call one narrow read against a fictional record. Verify its result, then try a record from another account. Test write retries with the same request identifier and confirm that a repeated call does not duplicate the business action.
4. Test the deployed process and its failures
Deploy the service, repeat the real client connection and read the deployed logs if it fails. Verify that revoking the client's access blocks later calls. Do not log tokens, connection strings or complete tool results containing personal data.
Restart or redeploy the test service and confirm that saved records remain available. Decide how a client learns whether a write committed if the connection closes before the response arrives. Longer operations need a durable job record and an appropriate worker design; keeping an instance awake is not a guarantee that the job survives a deployment.
When should I use another setup?
Use another host when the server requires a runtime or transport Prisma Compute does not support. Its current limits include no WebSocket server support and no persistent writable filesystem. It allows 60 seconds to begin responding to a request; that is a first-response deadline, not a promise that an in-memory task survives a restart.
Prisma Postgres credentials have full database access, with no custom roles. If the tool must use a database-enforced restricted role, choose a provider that supports restricted database roles. Otherwise keep the credential inside the server and make each tool's authorization boundary explicit. Hosting your own MCP server does not require exposing arbitrary SQL or database-management tools to its clients.
Frequently asked questions
Deploy the tools and their database together
Describe a TypeScript HTTP service and its Postgres dependency, then verify the tools through an authenticated client.