Connect Render to Claude with MCP

MCP · Render to Claude

Ask Claude about your Render database, in plain English

Connect Claude, Claude Code, Cursor or any MCP client to Query Streams once. Claude reads the structure of your Render database, writes the SQL, runs it read-only through the Agent that already sits with your data, and answers with the rows. No database password ever reaches the AI. About ten minutes, and the Free plan covers it.

About 10 minutes Claude, ChatGPT, Cursor + 11 more clients Credentials stay with you Read-only, always

What you’ll end up with

A Claude that can answer questions about your Render Postgres database with live, read-only queries, explain what the columns mean, and follow up when you ask for more — without ever seeing a database login, and without a firewall change: the Agent already inside your network runs the SQL and sends back only the rows. Once the Agent is in place, connecting Claude takes about 90 seconds if you are comfortable with a settings screen. Like this:

Claude ChatGPT Cursor Claude Code VS Code Windsurf Gemini CLI JetBrains Codex+5 moreRead-only

What is in customers in my Render database? Show me a few rows and tell me what each column means.

qs_get_table_schema qs_run_query schema_intelligence

I looked at the table structure first, then ran a read-only query through your Agent. Here are three of the customers rows:

customer_id	name	city
1042	Northwind Traders	Seattle
1057	Alpine Outfitters	Denver
1063	Harbour Foods	Halifax

customer_id identifies the row. name and city are described in your Schema Intelligence model, so I can filter on them by name.

Which three city values brought in the most revenue this quarter, and how does that compare with last quarter? Anything I should look into?

qs_get_relationships qs_run_query qs_run_query

I joined customers to orders on the relationship Schema Intelligence found, then ran one aggregate for each quarter. Both queries were read-only and returned 3 rows each:

city	This quarter	Last quarter	Change
Denver	184,200	133,900	+38%
Seattle	171,650	168,400	+2%
Halifax	96,300	129,700	−26%

Denver is the story: revenue up 38% on almost the same number of customers, so average order value rose. Halifax fell 26%, and the drop is two customers who ordered every month last quarter and not at all this quarter — worth a call before month end. Seattle is flat. Want the two Halifax accounts by name?

SELECT only, checked by the Agent logged on the MCP Activity tab 9 rows returned across 3 queries Same connection in 14 MCP clients

Rather not wire up an AI client at all? On the Business plan, Nova is the assistant built into Query Streams itself. It has every tool Claude gets here, plus the ones Claude does not: it drafts and validates the SQL against your Schema Intelligence model, turns the answer into a chart, and saves the result as a query your team can run from Excel, Google Sheets or the REST API — no key, no connector, nothing to install. Use MCP when your people already live in Claude, Cursor or ChatGPT; use Nova when you want the answers inside the Portal.

Render holds your data in the cloud, run by its provider. Claude, on the other hand, lives in a browser or a terminal and knows nothing about it. The usual bridge is pasting a schema into the chat and hoping, or handing an open-source MCP server your Render password. Query Streams does it differently: the Agent that already sits with your Render Postgres database runs the SQL Claude writes, read-only, and the MCP server in between checks who is asking, what they may do and how often. Claude gets answers. It never gets credentials.

Render runs managed PostgreSQL next to your Render services. The Agent reaches it over Render’s external hostname, which always uses TLS.

What you’ll need

A Query Streams account

MCP is on every plan, including Free. Free allows one key or one connected app, which is all this guide needs. Sign up at my.querystreams.com.

Render connected through the Agent

The Agent installed on any always-on computer, with the Render connection added in Data Agents.

Choose the Render card in the Portal. It pre-fills port 5432 and SSL on. Open your database in the Render Dashboard, click Connect, and copy the External connection string. Paste it and the host, database, user and password fill in. The internal URL only works inside Render, so the Agent cannot use it.

MCP switched on for you

Creators, owners and admins have it from the start. Everyone else needs an admin to flip the MCP switch beside their name under Account → Access Control. Until then the MCP page says “MCP is disabled for your account”.

An AI client

Claude on the web, Claude Desktop or the Claude mobile apps connect with no key. Claude Code, Cursor, ChatGPT and about ten other tools work too; the Portal has a ready-made recipe for each.

Set it up in four steps

1. Open MCP in the portal

   Sign in at my.querystreams.com and open Streams → Live → MCP. The page has four tabs: Connect, Connected Apps, My Keys and, for admins, Activity. Check the My Keys side panel while you are here: it lists your Render connector and whether Schema Intelligence has run on it. Complete coverage is what lets Claude write correct Render SQL on the first try.

   Open MCP

   Seeing “MCP is disabled for your account”? Your organization has MCP but your user is switched off. An admin turns it on with the MCP switch beside your name under Account → Access Control. Creators, owners and admins are on from the start.

2. Choose how you will connect

   There are two ways in, and they end at the same place:

   Chat apps · no key

   claude.ai, Claude Desktop, ChatGPT

   In Claude, Query Streams is in the Anthropic Connectors Directory: browse connectors, click Connect. Elsewhere you paste one address into the app, https://mcp.querystreams.com/mcp, and connect from a chat. A Query Streams page opens, you pick the organization and the permissions, and click Approve connection. Nothing to copy, nothing to keep secret. The connection appears under Connected Apps and can be revoked there.

   Developer tools · a key

   Claude Code, Cursor, VS Code and friends

   On My Keys click Generate key. Give it a Key name such as “Claude Code on my laptop”, keep Read and Execute ticked, choose an Expiration (Never, 30 days, 90 days or 1 year) and click Generate key. Copy it, then Continue to install: the Connect tab shows the exact snippet for your tool with the key already filled in.

   Both ways use the same three permissions, which you choose on the consent screen or on the key:

   Read

   List connectors, browse tables and columns, read your saved queries and alert rules. Never returns row data.

   Execute

   Run read-only SQL and saved queries through your Agent and return the rows. Without it Claude can describe your data but not answer from it.

   Analyze

   Profile tables, discover relationships and queue a Schema Intelligence run. It spends Nova AI credits and data allowance, so the consent screen never pre-ticks it.

   Lost the key? Open My Keys: the eye icon shows it again and Copy full key copies it. Revoke it there if a laptop goes missing; every client using it fails on its next call, within about five minutes.

3. Connect Claude

   Pick the recipe for the Claude you use. The server address is the same everywhere: https://mcp.querystreams.com/mcp.

   Claude on the web, Claude Desktop and mobile no key

   1. Open Settings → Connectors and click Browse connectors. Query Streams is listed in the Anthropic Connectors Directory: find Query Streams and click Connect. (Or open the directory listing directly and click Connect there.)
   2. If your organization hides directory connectors, click Add custom connector instead. Name it Query Streams, paste https://mcp.querystreams.com/mcp, leave the OAuth fields empty, click Add, then in any chat click + → Browse connectors → Query Streams → Connect.
   3. A Query Streams tab opens. Sign in if asked, pick the organization, review Read and Execute, optionally Limit to specific connectors, and click Approve connection.
   4. Back in Claude you see “Connected to Query Streams”. The first time Claude uses a tool it asks; choose Always allow.

   If you do add it by hand in Claude Desktop, use Settings → Connectors → Add, not the in-chat Add marketplace option, which expects a git repository. Connectors sync to your Claude account, so the mobile apps and Desktop pick it up automatically. Menu names are Anthropic’s and can move.

   Claude Code key

   One command, with your key from My Keys:

   Terminal

   claude mcp add --transport http querystreams https://mcp.querystreams.com/mcp \
     --header "X-MCP-Key: qsmcp_PASTE_YOUR_KEY_HERE"

   That writes the current project’s .mcp.json. Add --scope user to have Query Streams in every project. Run /mcp inside Claude Code to see it connected.

   Cursor key

   Open Cursor Settings → MCP → Add New MCP Server, or edit .cursor/mcp.json at the root of your workspace:

   .cursor/mcp.json

   {
     "mcpServers": {
       "querystreams": {
         "url": "https://mcp.querystreams.com/mcp",
         "headers": {
           "X-MCP-Key": "qsmcp_PASTE_YOUR_KEY_HERE"
         }
       }
     }
   }

   Restart Cursor or run MCP: Restart Servers; a querystreams badge appears in the MCP status bar.

   Using something else? The Connect tab has ready-to-paste recipes for ChatGPT, VS Code, Visual Studio, OpenAI Codex CLI, Gemini CLI, Windsurf, Zed, Cline, Continue.dev and JetBrains AI, plus a Paste & merge tool that drops the querystreams entry into a config file you already have. Any client that speaks MCP over HTTP works: server https://mcp.querystreams.com/mcp, header X-MCP-Key (an Authorization: Bearer header with the same key also works).

4. Ask your first question

   Start with something you already know the answer to, so you can see Claude reach for the right tool. Three that work well with your Render Postgres database:

   “What data do I have in my Render Postgres database?”

   Claude lists the tables it can see, tells you which have Schema Intelligence, and asks what you want to look at.

   “Show me ten rows from customers and explain each column.”

   Claude reads the table structure first (Read), then runs one SELECT through your Agent (Execute) and describes what name and city mean.

   “How many rows does customers have per city? Which city has the most?”

   Claude writes the GROUP BY in Render’s dialect, runs it, and answers in a sentence with a small table. Follow up in the same chat; it keeps the context.

   To confirm the wiring, ask “What Query Streams connectors do I have?”. Claude calls qs_list_connectors, and on My Keys the key’s Last used time updates within a few seconds. A connected app shows up under Connected Apps with the time it was connected and last used.

What Claude can do once connected

Claude sees nineteen small tools. You never call them yourself; Claude picks the right one for your question. In plain terms:

Why Schema Intelligence matters here

Every answer Claude receives is tagged with where the structure came from, and Claude adjusts how much it trusts what it sees.

If a database matters, run Schema Intelligence on it once from Nova → Intelligence. The My Keys tab shows a coverage panel per connector. How Schema Intelligence works.

What the plans allow

MCP is on every plan, including Free, with no separate fee. What each plan sets is how many keys or connected apps you can hold and how many calls a minute Claude may make:

A connected app counts as a key. On top of the per-minute figure, any one key may run at most 10 queries a minute. A query returns up to 1,000 rows and runs for up to 60 seconds unless Claude asks for more, to a ceiling of 50,000 rows and five minutes. The rows Claude receives count against your Data Realm allowance, the same pool your Excel and Sheets queries use, and MCP is measured before compression, so a wide result costs more here than the same rows in a spreadsheet. Schema Intelligence runs started from Claude spend Nova AI credits, exactly as they do from the Portal. See the pricing page for the allowances.

Keeping it safe

Good next moves

• Save the queries you consider canonical in Query Builder. Claude reaches for saved queries first, so “active customers” means what your team says it means.
• Use a Claude Project with Query Streams attached and put your house rules in its instructions: which Render database to use by default, which saved queries are the official definitions.
• Grant Analyze when you want deeper answers. Profiling a column before filtering on it is the difference between guessing a status code and using the right one. It spends Nova AI credits, so it is off until you say so.
• Ask for a chart. claude.ai draws charts from the rows Claude gets back.

When something doesn’t work

Questions people ask

Related guides

• Connect Microsoft SQL Server to Claude with MCP
• Connect PostgreSQL to Claude with MCP
• Connect MySQL to Claude with MCP
• Connect Microsoft Access to Claude with MCP
• Connect Query Streams to Claude via MCP: setup, permissions and troubleshooting
• All MCP guides