Neon + Claude
Connect Neon to Claude
Prepare a grounded database project inventory
Read projects with Claude and Agent200. Prepare a database project inventory within the configured Neon account scope.
On this page
Overview
Ask Claude for a focused database project inventory from one selected project. Compare its answer with the retrieved source and separate suggestions from recorded facts.
Start with one identified project. Preserve returned project, branch, database and operation fields; report missing data and keep the workflow read-only.
Provider reference: Neon API.
Use the provider credential described on the Neon parent page. Keep it in secure configuration and verify the selected tenant or account before reading.
- Connector
- Neon
- Works with
- Claude ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Neon enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect Neon to Claude
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Neon and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Neon project I identify and prepare a database project inventory. Name the source and use only project, branch, database and operation fields. State access gaps; do not change records.
What should come back
- The selected project is identified.
- Only the returned project, branch, database and operation fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected project ID, account scope, read permission and pagination. A project inventory is control-plane metadata, not database row access. Do not expose connection strings or credentials in an agent answer.
Get your API key
Create a key in the Agent200 dashboard. It reaches Neon and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Neon to Claude.
Goal: connect Neon to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/neon/framework/claude/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Neon is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands. 4. Check it works with this request: "Read the Neon project I identify and prepare a database project inventory. Name the source and use only project, branch, database and operation fields. State access gaps; do not change records." What should come back: - The selected project is identified. - Only the returned project, branch, database and operation fields are reported. - Access gaps and missing context are explicit; no source data is changed. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/neon/framework/claude.md
Neon tools Claude can call
-
List projects
Readneon_list_projectsFind projects visible to the Neon API key.
-
Read a project
Readneon_get_projectRetrieve one project by ID.
-
List branches
Readneon_list_branchesFind branches for an identified project.
-
Read a branch
Readneon_get_branchRetrieve one branch by ID.
-
List databases
Readneon_list_databasesFind databases on the selected branch.
No tool matches that search.
How it works
-
01
You ask Claude
In your own words, for something in Neon.
-
02
Claude picks a tool
It sees the Neon tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Neon with your Agent200 API key, within the endpoints your project allows.
-
04
Claude answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
The source cannot be read
Check the selected project ID, account scope, read permission and pagination. A project inventory is control-plane metadata, not database row access. Do not expose connection strings or credentials in an agent answer.
FAQ
How do I verify this result?
Compare the named project and returned project, branch, database and operation fields with the source. Treat missing information as missing, not as a fact.
