# How to connect Listen Notes to Hermes Agent (paste one key, 26 tools)

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

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

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

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

Verify the connection by asking Hermes:

> Use Listen Notes to batch fetch basic meta data for episodes 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 Listen Notes is connected in the dashboard, that agent calls the same 26 Listen Notes 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).

## Listen Notes MCP for Hermes

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

## What the Hermes Agent Listen Notes integration can do

26 Listen Notes 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 26.

### 25 of 26 Listen Notes tools for Hermes

| Tool | What it does |
|---|---|
| **Batch fetch basic meta data for episodes** `listennotes_batch_fetch_basic_meta_data_for_episodes` | The listennotestest_episodes_post endpoint allows users to retrieve metadata for multiple |
| **Batch fetch basic meta data for podcasts** `listennotes_batch_fetch_basic_meta_data_for_podcasts` | The listennotestest_podcasts_post endpoint allows users to retrieve information about multiple |
| **Fetch a curated list of podcasts by ID** `listennotes_fetch_a_curated_list_of_podcasts_by_id` | Retrieves detailed information about a specific curated podcast using its unique identifier |
| **Fetch a list of best podcasts by genre** `listennotes_fetch_a_list_of_best_podcasts_by_genre` | The getBestPodcasts endpoint retrieves a curated list of the best podcasts from the Listen |
| **Fetch a list of podcast genres** `listennotes_fetch_a_list_of_podcast_genres` | The GetGenres endpoint retrieves a comprehensive list of available genres within the |
| **Fetch a list of your playlists** `listennotes_fetch_a_list_of_your_playlists` | Retrieves a list of playlists from the Listen Notes platform |
| **Fetch a random podcast episode** `listennotes_fetch_a_random_podcast_episode` | The 'just_listen' endpoint is a basic listener or health check mechanism for the |
| **Fetch audience demographics for a podcast** `listennotes_fetch_audience_demographics_for_a_podcast` | Retrieves audience information for a specific podcast identified by its unique ID |
| **Fetch curated lists of podcasts** `listennotes_fetch_curated_lists_of_podcasts` | Retrieves a list of curated podcasts from the Listen Notes platform |
| **Fetch detailed meta data for an episode by ID** `listennotes_fetch_detailed_meta_data_for_an_episode_by_id` | Retrieves detailed information about a specific episode using its unique identifier |
| **Fetch podcast episodes by ID** `listennotes_fetch_podcast_episodes_by_id` | Retrieves detailed information about a specific podcast using its unique identifier |
| **Fetch podcast languages** `listennotes_fetch_podcast_languages` | Retrieves a list of supported languages in the Listen Notes API |
| **Fetch podcasts by a publisher s domain name** `listennotes_fetch_podcasts_by_a_publisher_s_domain_name` | Retrieves a list of podcasts associated with a specified domain name |
| **Fetch recommendations for a podcast** `listennotes_fetch_recommendations_for_a_podcast` | Retrieves a list of podcast recommendations based on a specified podcast ID |
| **Fetch recommendations for an episode** `listennotes_fetch_recommendations_for_an_episode` | Retrieves a list of recommended podcast episodes based on a specific episode ID |
| **Fetch related search terms** `listennotes_fetch_related_search_terms` | Retrieves a list of related search queries based on the current context or user's recent search |
| **Fetch supported regions** `listennotes_fetch_supported_regions` | Retrieves information about available regions in the listennotestest platform |
| **Fetch trending search terms** `listennotes_fetch_trending_search_terms` | Retrieves a list of currently trending search terms related to podcasts |
| **Find episodes by title** `listennotes_find_episodes_by_title` | The search_episode_titles endpoint allows users to search for and retrieve episode titles based |
| **Full text search** `listennotes_full_text_search` | The search endpoint allows users to query notifications or events within the listennotestest |
| **Get playlist by ID** `listennotes_get_playlist_by_id` | Retrieves detailed information about a specific playlist using its unique identifier |
| **Refresh rss feed of a podcast** `listennotes_refresh_rss_feed_of_a_podcast` | Retrieves or generates an RSS feed for a specific podcast identified by its unique ID |
| **Spell check on a search term** `listennotes_spell_check_on_a_search_term` | The spellcheck endpoint provides a spell-checking service for text input |
| **Typeahead search** `listennotes_typeahead_search` | The typeahead endpoint provides real-time search suggestions as users type their queries |
| **Submit a podcast to listen notes database** `listennotes_submit_a_podcast_to_listen_notes_database` | The submit_podcast endpoint allows users to submit a podcast for inclusion in the Listen Notes |

## Example prompts

**Batch Fetch Basic Meta Data For Episodes**

> Use Listen Notes to batch fetch basic meta data for episodes and walk me through the result in plain English.

**Batch Fetch Basic Meta Data For Podcasts**

> Use Listen Notes to batch fetch basic meta data for podcasts and walk me through the result in plain English.

**Fetch A Curated List Of Podcasts By Id**

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

**Fetch A List Of Best Podcasts By Genre**

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

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

## ClawLink vs. Composio

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

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

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

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

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

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

- [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.
- [Penpot](https://claw-link.dev/hermes/penpot) — Open-source design and prototyping platform for collaborative design workflows.
- [Canva](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates
