# How to connect NocoDB to Hermes Agent (paste one key, 28 tools)

> Connect NocoDB to Hermes 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/hermes/nocodb

Most guides for giving Hermes Agent NocoDB access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical NocoDB setup: pair once in the browser and your always-on Hermes agent can act on NocoDB for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to NocoDB.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect NocoDB** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent 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 <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect NocoDB in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your NocoDB API key once.

Verify the connection by asking Hermes:

> Use NocoDB to auth me and walk me through the result in plain English.

### Using a different agent?

The Hermes 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 Hermes

Looking for a NocoDB MCP server for Hermes Agent? ClawLink connects NocoDB to Hermes Agent 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 OpenClaw instead? The [OpenClaw NocoDB integration](https://claw-link.dev/openclaw/nocodb) works the same way.

## What the Hermes Agent NocoDB integration can do

28 NocoDB tools are ready for Hermes Agent 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 Hermes

| 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 Hermes Agent. 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 Hermes Agent 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.

### Hermes paired but still can't use NocoDB
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### 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 Hermes Agent NocoDB integration?
Yes. ClawLink is the fastest way to connect Hermes to NocoDB: link your NocoDB account once in the browser and Hermes Agent can call the NocoDB API through 28 ready-made tools — no custom code or token handling.

### How do I connect NocoDB to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect NocoDB in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to NocoDB in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want NocoDB working from chat.

### Hermes paired but still can't use NocoDB
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [PostHog tools](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags
- [Hermes DataforSEO integration](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits
- [Metabase tools](https://claw-link.dev/hermes/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.
