Neon + OpenClaw
Connect Neon to OpenClaw
Prepare a grounded database project inventory
Read projects with OpenClaw and Agent200. Prepare a database project inventory within the configured Neon account scope.
On this page
Overview
Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one project the user can access. A saved setting alone does not verify the read.
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
- OpenClaw ยท 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.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Neon to OpenClaw
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Configure Neon access
Use the provider-issued credential through the supported Agent200 connection route. Confirm the account scope and inspect the advertised tools before reading.
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 OpenClaw.
Goal: connect Neon to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/neon/framework/openclaw/ 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 OpenClaw'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 OpenClaw: 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 OpenClaw'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/openclaw.md
Neon tools OpenClaw 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 OpenClaw
In your own words, for something in Neon.
-
02
OpenClaw 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
OpenClaw 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.
