# How to connect Baserow to Hermes Agent (paste one key, 14 tools) > Connect Baserow to Hermes with ClawLink: paste your Baserow key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/baserow Most guides for giving Hermes Agent Baserow 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 Baserow setup: pair once in the browser and your always-on Hermes agent can act on Baserow 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 Baserow. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Baserow** — 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 baserow # connect Baserow (browser OAuth) npx -y @useclawlink/cli actions baserow # list available actions npx -y @useclawlink/cli run baserow --input '' # 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 Baserow in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Baserow API key once. Verify the connection by asking Hermes: > Pull the relevant data from Baserow, summarize it in plain English, and point out anything that needs attention. ### 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 Baserow is connected in the dashboard, that agent calls the same 14 Baserow 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). ## Baserow MCP for Hermes Looking for a Baserow MCP server for Hermes Agent? ClawLink connects Baserow to Hermes Agent and exposes 14 Baserow 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 Baserow integration](https://claw-link.dev/openclaw/baserow) works the same way. ## What the Hermes Agent Baserow integration can do 14 Baserow tools are ready for Hermes Agent once the account is connected. ### All 14 Baserow tools for Hermes | Tool | What it does | |---|---| | **Get form view metadata** `baserow_get_form_view_metadata` | Retrieve metadata for a Baserow form view | | **Get public builder by domain name** `baserow_get_public_builder_by_domain_name` | Retrieve the public published version of a builder by its domain name | | **Get record names builder page data source** `baserow_get_record_names_builder_page_data_source` | Find the record names associated with a given list of record ids | | **Get settings** `baserow_get_settings` | Retrieve all admin configured settings for the Baserow instance | | **List application user sources** `baserow_list_application_user_sources` | List all user sources of an application if the user has access to the related application's | | **List auth providers login options** `baserow_list_auth_providers_login_options` | List available login options for configured authentication providers | | **List databases** `baserow_list_databases` | Retrieves a list of all databases in a specified workspace | | **List tables** `baserow_list_tables` | Lists all tables within a specified Baserow database | | **List templates** `baserow_list_templates` | List all template categories and their related templates | | **Create user** `baserow_create_user` | Create a new Baserow user with the provided details | | **Dispatch builder page data source** `baserow_dispatch_builder_page_data_source` | Dispatch the service of a builder page data source and return the result | | **Dispatch public builder page data source** `baserow_dispatch_public_builder_page_data_source` | Dispatch the service of a published builder page data source and return the result | | **Send password reset email** `baserow_send_password_reset_email` | Send a password reset email to a user's email address | | **Send verify email** `baserow_send_verify_email` | Send a verification email to a user's email address | ## Example prompts **Get Form View Metadata** > Pull the relevant data from Baserow, summarize it in plain English, and point out anything that needs attention. **Get Public Builder By Domain Name** > Pull the relevant data from Baserow, summarize it in plain English, and point out anything that needs attention. **Get Record Names Builder Page Data Source** > Pull the relevant data from Baserow, summarize it in plain English, and point out anything that needs attention. **Get Settings** > Pull the relevant data from Baserow, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Baserow working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Baserow API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Baserow 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 Baserow. | 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 Baserow actions to the runtime in a format your agent can reliably use. | 14 tools for Baserow are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Baserow 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 Baserow in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Baserow 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 Baserow 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 Baserow 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 Baserow tools Baserow 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 Baserow 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. ### Baserow 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 Baserow 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 Baserow integration? Yes. ClawLink is the fastest way to connect Hermes to Baserow: link your Baserow account once in the browser and Hermes Agent can call the Baserow API through 14 ready-made tools — no custom code or token handling. ### How do I connect Baserow 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 Baserow in the dashboard and Hermes can use it from the next message — no config files, and the Baserow key you paste is stored server-side instead of in your environment. ### How long does it take to connect Baserow to Hermes Agent? About two minutes. Sign in, click Connect next to Baserow in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Baserow 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 Baserow working from chat. ### Hermes paired but still can't use Baserow 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 - [Connect Metabase](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.