# How to connect Xata to Hermes Agent (paste one key, 8 tools)

> Connect Xata to Hermes with ClawLink: paste your Xata key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/xata

Most guides for giving Hermes Agent Xata 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 Xata setup: pair once in the browser and your always-on Hermes agent can act on Xata 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 Xata.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Xata** — 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 xata  # connect Xata (browser OAuth)
npx -y @useclawlink/cli actions xata  # list available actions
npx -y @useclawlink/cli run xata <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 Xata in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Xata API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Xata, 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 Xata is connected in the dashboard, that agent calls the same 8 Xata 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).

## Xata MCP for Hermes

Looking for a Xata MCP server for Hermes Agent? ClawLink connects Xata to Hermes Agent and exposes 8 Xata 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 Xata integration](https://claw-link.dev/openclaw/xata) works the same way.

## What the Hermes Agent Xata integration can do

8 Xata tools are ready for Hermes Agent once the account is connected.

### All 8 Xata tools for Hermes

| Tool | What it does |
|---|---|
| **Get organization** `xata_get_organization` | Retrieve detailed information about a specific organization by its ID |
| **Get project limits** `xata_get_project_limits` | Retrieve the default resource limits for projects in a specified organization |
| **List extensions** `xata_list_extensions` | Get available PostgreSQL extensions for a specific image |
| **List images** `xata_list_images` | Retrieve a list of all available postgres images for a specified organization and region |
| **List instance types** `xata_list_instance_types` | Retrieve a list of all instance types for the specified organization and region |
| **List org API keys** `xata_list_org_api_keys` | Retrieve a list of API keys for a specific Xata organization |
| **List regions** `xata_list_regions` | Retrieve a list of all regions where new branches can be deployed for the specified organization |
| **Update organization** `xata_update_organization` | Update information for an existing organization, such as its name |

## Example prompts

**Get Organization**

> Pull the relevant data from Xata, summarize it in plain English, and point out anything that needs attention.

**Get Project Limits**

> Pull the relevant data from Xata, summarize it in plain English, and point out anything that needs attention.

**List Extensions**

> List the relevant items in Xata, group them by priority, and recommend what Hermes should do next.

**List Images**

> List the relevant items in Xata, group them by priority, and recommend what Hermes should do next.

## 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 Xata working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Xata API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Xata 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 Xata. | 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 Xata actions to the runtime in a format your agent can reliably use. | 8 tools for Xata are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Xata 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 Xata in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Xata 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 Xata
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 Xata 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 Xata tools
Xata 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 Xata 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.

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

### How do I connect Xata 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 Xata in the dashboard and Hermes can use it from the next message — no config files, and the Xata key you paste is stored server-side instead of in your environment.

### How long does it take to connect Xata to Hermes Agent?
About two minutes. Sign in, click Connect next to Xata in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Xata 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 Xata working from chat.

### Hermes paired but still can't use Xata
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

- [Hermes PostHog integration](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags
- [DataforSEO](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.