# How to connect Metatextai to Hermes Agent (paste one key, 13 tools)

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

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

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

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

Verify the connection by asking Hermes:

> Use Metatextai to chat completions 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 Metatextai is connected in the dashboard, that agent calls the same 13 Metatextai 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).

## Metatextai MCP for Hermes

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

## What the Hermes Agent Metatextai integration can do

13 Metatextai tools are ready for Hermes Agent once the account is connected. The 12 below are the ones people reach for most; your agent can call all 13.

### 12 of 13 Metatextai tools for Hermes

| Tool | What it does |
|---|---|
| **Chat completions** `metatextai_chat_completions` | Generate chat completions |
| **Classify** `metatextai_classify` | Classify text |
| **Evaluate** `metatextai_evaluate` | Evaluate LLM messages against policies/guardrails |
| **Extract** `metatextai_extract` | Run information extraction |
| **Generate** `metatextai_generate` | Generate text for a project model |
| **List applications** `metatextai_list_applications` | Retrieve a list of all existing applications |
| **List models** `metatextai_list_models` | Retrieve a list of all available models and their supported tasks |
| **List policies guardrails** `metatextai_list_policies_guardrails` | List all guardrail policies for a specific application |
| **List red team test probes** `metatextai_list_red_team_test_probes` | List all available red team test probes |
| **Create policy guardrails** `metatextai_create_policy_guardrails` | Create a policy guardrail |
| **Run red team test scan** `metatextai_run_red_team_test_scan` | Run a vulnerability red-team test scan |
| **Update policy guardrails** `metatextai_update_policy_guardrails` | Update an existing policy's guardrails |

## Example prompts

**Chat Completions**

> Use Metatextai to chat completions and walk me through the result in plain English.

**Classify**

> Use Metatextai to classify and walk me through the result in plain English.

**Evaluate**

> Use Metatextai to evaluate and walk me through the result in plain English.

**Extract**

> Use Metatextai to extract 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 Metatextai working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use Metatextai
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 DataRobot integration](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
- [Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
- [Hermes Just One API integration](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.
