How to connect Neon to OpenClaw
Connect Neon to OpenClaw with ClawLink: paste your Neon key once and 107 tools work from chat. No MCP server to run, nothing stored on your machine.
NeonAPI KEYMCPServerless Postgres with branching and scale-to-zero. Once connected, OpenClaw can read and act on Neon from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Neon access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Neon setup: install one ClawHub skill, connect Neon in the browser, and OpenClaw can call real Neon actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Neon skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Neon" (hith3sh/neon-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/neon-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Neon.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Neon
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Neon?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Neon in the ClawLink dashboard — paste your Neon API key once.
Verify the connection by asking OpenClaw:
Use Neon to accept projects transfer requests and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Neon is connected in the dashboard, that agent calls the same 107 Neon tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Neon MCP for OpenClaw
Looking for a Neon MCP server for OpenClaw? ClawLink connects Neon to OpenClaw and exposes 107 Neon tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Neon integration works the same way.
What the OpenClaw Neon integration can do
107 Neon tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 107.
30 of 107 Neon tools for OpenClaw
| Tool | What it does |
|---|---|
Accept projects transfer requests neon_accept_projects_transfer_requests | Accept a transfer request for a project |
Access project details by ID neon_access_project_details_by_id | Retrieve detailed information about a Neon project |
Add new jwks to project endpoint neon_add_new_jwks_to_project_endpoint | Add a new JWKS URL to a project |
Add project email permission neon_add_project_email_permission | Add email permissions to a project |
Add role to branch neon_add_role_to_branch | Create a new PostgreSQL role within a branch |
Count project branches neon_count_project_branches | Get the total number of branches in a project |
Fetch database for branch neon_fetch_database_for_branch | List databases for a project branch |
Get auth neon_get_auth | Retrieve authentication information |
Fetch organization members by ID neon_fetch_organization_members_by_id | Retrieves a list of all members associated with a specific organization in the Neon B2B SaaS |
Fetch vpcendpoint details by ID neon_fetch_vpcendpoint_details_by_id | Retrieves the current state and configuration details of a specific VPC endpoint assigned to a |
Get auth allow localhost neon_get_auth_allow_localhost | Retrieves the allow localhost configuration for a specific branch in a Neon project |
Get auth email provider neon_get_auth_email_provider | Retrieves the email provider configuration for Neon Auth on a specific branch |
Get available preload libraries neon_get_available_preload_libraries | Retrieves the list of available shared preload libraries for a Neon project |
Get branch roles for project neon_get_branch_roles_for_project | Retrieves the roles associated with a specific branch within a project in the Neon B2B SaaS |
Get branches anonymized status neon_get_branches_anonymized_status | Retrieves the current status of an anonymized branch, including its state and progress |
Get branches backup schedule neon_get_branches_backup_schedule | Retrieves the backup schedule configuration for a specified branch within a Neon project |
Get branches data API neon_get_branches_data_api | Retrieves the Neon Data API information for a specific branch and database |
Get branches for project neon_get_branches_for_project | Retrieves a list of branches associated with a specific project in the Neon B2B SaaS |
Get branches masking rules neon_get_branches_masking_rules | Retrieves the masking rules for the specified anonymized branch |
Get consumption history projects neon_get_consumption_history_projects | Retrieves consumption history for projects within a Neon organization |
Get current user information neon_get_current_user_information | Retrieves the profile information for the currently authenticated user |
Get organization API keys neon_get_organization_api_keys | Retrieves a list of all API keys associated with a specific organization in the Neon B2B SaaS |
Get project branch role neon_get_project_branch_role | Retrieves detailed information about a specific role within a particular branch of a Neon |
Get project branch schema comparison neon_get_project_branch_schema_comparison | Compares the database schema of a branch with another branch's schema in a Neon project |
Get project branches neon_get_project_branches | Retrieves detailed information about a specific branch within a Neon project |
Get project connection uri neon_get_project_connection_uri | Retrieves the connection URI for a specified project within the Neon B2B SaaS integration |
Get project endpoint information neon_get_project_endpoint_information | Retrieves a list of all compute endpoints associated with a specific Neon project |
Get project operation by ID neon_get_project_operation_by_id | Retrieves detailed information about a specific operation within a Neon serverless PostgreSQL |
Get schema for project branch neon_get_schema_for_project_branch | Retrieves the PostgreSQL database schema (DDL) for a specific database on a branch within a |
Get user organizations neon_get_user_organizations | Retrieves a list of organizations associated with the currently authenticated user in the Neon |
Try it: find the Neon tool you need
Browse the 30 Neon tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Neon to accept projects transfer requests and walk me through the result in plain English.
Use Neon to access project details by id and walk me through the result in plain English.
Use Neon to add new jwks to project endpoint and walk me through the result in plain English.
Use Neon to add project email permission and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Neon working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Neon API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Neon account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Neon. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Neon actions to the runtime in a format your agent can reliably use. | 107 tools for Neon are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Neon to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Neon in the browser, and the 107 tools above work from chat. There is no SDK and no config file, and the Neon key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Neon skill but can't call the tools
The ClawHub skill teaches OpenClaw about Neon, but the calls run through the ClawLink plugin and your connected account. Make sure Neon is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Neon from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Neon tools
Neon tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Neon call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Neon returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Neon has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Neon integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Neon: link your Neon account once in the browser and OpenClaw can call the Neon API through 107 ready-made tools — no custom code or token handling.
How do I add Neon to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Neon skill from ClawHub, then you click Connect in the dashboard to authorize Neon. OpenClaw calls the tools from the next message — no config files, and the Neon key you paste is stored server-side instead of in your environment.
How long does it take to connect Neon to OpenClaw?
About two minutes. Sign in, click Connect next to Neon in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Neon up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Neon working from chat.
OpenClaw installed the Neon skill but can't call the tools
The ClawHub skill teaches OpenClaw about Neon, but the calls run through the ClawLink plugin and your connected account. Make sure Neon is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
