# How to connect Amara to Hermes Agent (paste one key, 30 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Amara MCP for Hermes

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

## What the Hermes Agent Amara integration can do

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

### 29 of 30 Amara tools for Hermes

| Tool | What it does |
|---|---|
| **Fetch subtitles data** `amara_fetch_subtitles_data` | Fetch subtitle data for a video in a specific language |
| **Get activity** `amara_get_activity` | Retrieve detailed information about a specific activity by its ID |
| **Get subtitle language details** `amara_get_subtitle_language_details` | Retrieve details for a single subtitle language |
| **Get team details** `amara_get_team_details` | Get details on a specific team by slug |
| **Get team languages** `amara_get_team_languages` | Get language preferences for a specific team by slug |
| **Get user activity** `amara_get_user_activity` | Retrieve activity log for a specific user on Amara |
| **Get user data** `amara_get_user_data` | Retrieves detailed user profile information from Amara, including username, avatar, biography |
| **Get video URL** `amara_get_video_url` | Get details for a specific video URL |
| **Get video URL details** `amara_get_video_url_details` | Get details for a specific video URL |
| **List activity** `amara_list_activity` | List activity across Amara |
| **List available languages** `amara_list_available_languages` | Get a list of all supported languages |
| **List subtitle actions** `amara_list_subtitle_actions` | List available actions for subtitles based on current workflow state |
| **List subtitle languages** `amara_list_subtitle_languages` | List all subtitle languages for a video |
| **List subtitle notes** `amara_list_subtitle_notes` | List notes for subtitles in a specific language |
| **List teams** `amara_list_teams` | List all teams |
| **List video activity** `amara_list_video_activity` | List activity for a specific video |
| **List video URLS** `amara_list_video_urls` | List all URLs associated with a video |
| **List videos** `amara_list_videos` | List all videos |
| **View video details** `amara_view_video_details` | View details of a specific video by ID |
| **Add subtitle note** `amara_add_subtitle_note` | Adds a note/comment to a specific subtitle language for a video |
| **Add video URL** `amara_add_video_url` | Add a new URL to a video, allowing association with multiple video providers (YouTube, Vimeo |
| **Create subtitle language** `amara_create_subtitle_language` | Creates a new subtitle language track for an Amara video |
| **Create subtitles** `amara_create_subtitles` | Create new subtitles for a video in a specific language |
| **Create video** `amara_create_video` | Add a new video to Amara |
| **Make video URL primary** `amara_make_video_url_primary` | Set a video URL as the primary URL |
| **Perform subtitle action** `amara_perform_subtitle_action` | Perform an action on subtitles such as publish, unpublish, approve, reject, send-back, or |
| **Send message** `amara_send_message` | Sends a message to a user or team member in Amara |
| **Update subtitle language** `amara_update_subtitle_language` | Update a subtitle language for a video |
| **Update video** `amara_update_video` | Update an existing video's metadata including title, description, team, and project assignment |

## Example prompts

**Fetch Subtitles Data**

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

**Get Activity**

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

**Get Subtitle Language Details**

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

**Get Team Details**

> Pull the relevant data from Amara, 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 Amara working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

- [Connect Cloudinary](https://claw-link.dev/hermes/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN.
- [Hermes Penpot integration](https://claw-link.dev/hermes/penpot) — Open-source design and prototyping platform for collaborative design workflows.
- [Canva tools](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates