# How to connect Neon to OpenClaw > Connect Neon to OpenClaw in one click. 8 Neon tools your agent can call from chat. No API keys. Web version: https://claw-link.dev/openclaw/neon ClawLink gives OpenClaw a more practical Neon setup than rolling your own integration. 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. ## Neon MCP for OpenClaw Looking for a Neon MCP server for OpenClaw? ClawLink connects Neon to OpenClaw and exposes 8 Neon tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Neon integration](https://claw-link.dev/hermes/neon) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/neon ## Setup It takes three steps to connect OpenClaw to Neon. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Neon** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect neon # connect Neon (browser OAuth) npx -y @useclawlink/cli actions neon # list available actions npx -y @useclawlink/cli run neon --input '' # execute (add --confirm for writes) ``` ## What the OpenClaw Neon integration can do 8 Neon tools are ready for OpenClaw once the account is connected. ### All 8 Neon tools for OpenClaw | Tool | What it does | |---|---| | **Access project details by ID** `neon_access_project_details_by_id` | Retrieve detailed information about a Neon project | | **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 | | **Accept projects transfer requests** `neon_accept_projects_transfer_requests` | Accept a transfer request for a project | | **Add role to branch** `neon_add_role_to_branch` | Create a new PostgreSQL role within a branch | | **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 | ## Example prompts **Access Project Details By Id** > Use Neon to access project details by id and walk me through the result in plain English. **Count Project Branches** > Use Neon to count project branches and walk me through the result in plain English. **Fetch Database For Branch** > Pull the relevant data from Neon, summarize it in plain English, and point out anything that needs attention. **Get Auth** > Pull the relevant data from Neon, summarize it in plain English, and point out anything that needs attention. ## 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. | 8 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 8 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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. ### The Neon account is connected but the action fails Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, 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. ### 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 8 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 or API keys. ### 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. ## Related - [Supabase tools](https://claw-link.dev/openclaw/supabase) — Query and manage Postgres databases - [Dropbox](https://claw-link.dev/openclaw/dropbox) — Store, sync, and share files - [Box](https://claw-link.dev/openclaw/box) — Store, share, and manage files and folders