# How to connect NocoDB to OpenClaw (paste one key, 28 tools) > Connect NocoDB to OpenClaw with ClawLink: paste your NocoDB key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/nocodb The usual route to NocoDB 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 NocoDB setup: install one ClawHub skill, connect NocoDB in the browser, and OpenClaw can call real NocoDB actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to NocoDB. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect NocoDB** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 nocodb # connect NocoDB (browser OAuth) npx -y @useclawlink/cli actions nocodb # list available actions npx -y @useclawlink/cli run nocodb --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 NocoDB in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your NocoDB API key once. Verify the connection by asking OpenClaw: > Use NocoDB to auth me 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once NocoDB is connected in the dashboard, that agent calls the same 28 NocoDB tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## NocoDB MCP for OpenClaw Looking for a NocoDB MCP server for OpenClaw? ClawLink connects NocoDB to OpenClaw and exposes 28 NocoDB 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 NocoDB integration](https://claw-link.dev/hermes/nocodb) works the same way. ## What the OpenClaw NocoDB integration can do 28 NocoDB tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 28. ### 25 of 28 NocoDB tools for OpenClaw | Tool | What it does | |---|---| | **Auth me** `nocodb_auth_me` | Get authenticated user information including email, name, roles, and profile details | | **Db table sort get** `nocodb_db_table_sort_get` | Retrieve sort configuration by ID from NocoDB | | **Integrations info** `nocodb_integrations_info` | Retrieve metadata for a specific NocoDB integration by type and subtype | | **Integrations list** `nocodb_integrations_list` | Retrieve all available integrations in NocoDB | | **List workspaces** `nocodb_list_workspaces` | List all workspaces accessible to the authenticated user | | **Notification list** `nocodb_notification_list` | Retrieve paginated notification records for the authenticated user | | **Notification poll** `nocodb_notification_poll` | Poll for notifications using long-polling mechanism | | **Plugin status** `nocodb_plugin_status` | Check if a NocoDB plugin is active or not | | **Public grouped data list** `nocodb_public_grouped_data_list` | Retrieve grouped data from a publicly shared NocoDB view | | **Table read** `nocodb_table_read` | Retrieve complete schema information for a specific table | | **Utils aggregated meta info** `nocodb_utils_aggregated_meta_info` | Get aggregated meta information such as tableCount, dbViewCount, viewCount and other statistics | | **Utils app health** `nocodb_utils_app_health` | Get the NocoDB application health status | | **Utils app info** `nocodb_utils_app_info` | Get comprehensive NocoDB application information including authentication settings, version | | **Utils cloud features** `nocodb_utils_cloud_features` | Get NocoDB Cloud features | | **Utils command palette** `nocodb_utils_command_palette` | Get dynamic command palette suggestions based on scope | | **Utils feed** `nocodb_utils_feed` | Get NocoDB product feed from social media sources including GitHub, YouTube, Twitter, and Cloud | | **Utils URL to config** `nocodb_utils_url_to_config` | Convert JDBC URL or database connection URL to connection configuration object | | **Workspace base list** `nocodb_workspace_base_list` | List all bases in a NocoDB workspace | | **Auth password forgot** `nocodb_auth_password_forgot` | Initiate password reset process by sending a reset email to the user | | **Db view column update** `nocodb_db_view_column_update` | Update a column configuration in a view | | **Integration store** `nocodb_integration_store` | Store configuration for a NocoDB integration | | **Storage upload by URL** `nocodb_storage_upload_by_url` | Upload attachments from remote URLs to NocoDB storage | | **User profile update** `nocodb_user_profile_update` | Update authenticated user's profile information including display name, first name, and last | | **Utils error report** `nocodb_utils_error_report` | Report errors to NocoDB's error tracking system | | **Auth signout** `nocodb_auth_signout` | Sign out the authenticated user and clear their refresh token from the database and cookie | ## Example prompts **Auth Me** > Use NocoDB to auth me and walk me through the result in plain English. **Db Table Sort Get** > Use NocoDB to db table sort get and walk me through the result in plain English. **Integrations Info** > Use NocoDB to integrations info and walk me through the result in plain English. **Integrations List** > Use NocoDB to integrations list 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 NocoDB working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the NocoDB API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected NocoDB 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 NocoDB. | 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 NocoDB actions to the runtime in a format your agent can reliably use. | 28 tools for NocoDB are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes NocoDB 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 NocoDB in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the NocoDB key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the NocoDB skill but can't call the tools The ClawHub skill teaches OpenClaw about NocoDB, but the calls run through the ClawLink plugin and your connected account. Make sure NocoDB 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 NocoDB 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 NocoDB tools NocoDB 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 NocoDB 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. ### NocoDB 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 NocoDB has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw NocoDB integration? Yes. ClawLink is the fastest way to connect OpenClaw to NocoDB: link your NocoDB account once in the browser and OpenClaw can call the NocoDB API through 28 ready-made tools — no custom code or token handling. ### How do I add NocoDB to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink NocoDB skill from ClawHub, then you click Connect in the dashboard to authorize NocoDB. OpenClaw calls the tools from the next message — no config files, and the NocoDB key you paste is stored server-side instead of in your environment. ### How long does it take to connect NocoDB to OpenClaw? About two minutes. Sign in, click Connect next to NocoDB in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring NocoDB 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 NocoDB working from chat. ### OpenClaw installed the NocoDB skill but can't call the tools The ClawHub skill teaches OpenClaw about NocoDB, but the calls run through the ClawLink plugin and your connected account. Make sure NocoDB 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 - [Connect PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [Connect DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.