# How to connect Stormboard to Hermes Agent (paste one key, 41 tools)

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

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

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

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

Verify the connection by asking Hermes:

> Use Stormboard to check authentication 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 Stormboard is connected in the dashboard, that agent calls the same 41 Stormboard 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).

## Stormboard MCP for Hermes

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

## What the Hermes Agent Stormboard integration can do

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

### 30 of 41 Stormboard tools for Hermes

| Tool | What it does |
|---|---|
| **Check authentication** `stormboard_check_authentication` | Verify API key authentication validity |
| **Details** `stormboard_details` | Retrieve detailed information about a specific Storm |
| **Get a list of connectors in a storm** `stormboard_get_a_list_of_connectors_in_a_storm` | Retrieve a list of connectors within a specific Storm |
| **Get a list of ideas** `stormboard_get_a_list_of_ideas` | Retrieve all ideas from a Storm |
| **Get a list of participants** `stormboard_get_a_list_of_participants` | Retrieve a list of all participants in a Storm |
| **Get a list of storms invites** `stormboard_get_a_list_of_storms_invites` | Retrieve a list of storms that you have been invited to |
| **Get a list of tags in the storm** `stormboard_get_a_list_of_tags_in_the_storm` | Retrieve the list of tags that have been created in a Storm |
| **Get a list of your storms** `stormboard_get_a_list_of_your_storms` | Retrieve a list of storms from Stormboard |
| **Get authentication info** `stormboard_get_authentication_info` | Retrieve authentication information and API token for the authenticated user |
| **Get chat messages** `stormboard_get_chat_messages` | Retrieve a list of chat messages from a Stormboard storm |
| **Get idea data** `stormboard_get_idea_data` | Retrieve detailed data and metadata for a specific idea |
| **Get info about your user** `stormboard_get_info_about_your_user` | Retrieve authenticated user profile information |
| **Get my storm access** `stormboard_get_my_storm_access` | Check if the authenticated user has access to a Storm and retrieve their permission level |
| **Get storm template** `stormboard_get_storm_template` | Retrieve template data for a Storm including all sections and subsections |
| **Get tag data for an idea** `stormboard_get_tag_data_for_an_idea` | Retrieve tag data for a specific idea in Stormboard |
| **Get unread chat messages** `stormboard_get_unread_chat_messages` | Retrieve unread chat messages from a specific Storm |
| **Accept a storm invite** `stormboard_accept_a_storm_invite` | Accept a Storm invitation and join the Storm |
| **Add a favorite star** `stormboard_add_a_favorite_star` | Add a favorite star to a Storm on the Dashboard |
| **Close a storm** `stormboard_close_a_storm` | Close an open Storm, making it read-only |
| **Create a line connector** `stormboard_create_a_line_connector` | Create a line connector between two ideas |
| **Create a new chat messages** `stormboard_create_a_new_chat_messages` | Create a new chat message in a Stormboard storm |
| **Create a new storm** `stormboard_create_a_new_storm` | Create a new Storm in Stormboard for interactive planning and collaboration |
| **Create a new tag** `stormboard_create_a_new_tag` | Create a new tag in a Storm without any data related to Ideas |
| **Create a new user** `stormboard_create_a_new_user` | Create a new user account in Stormboard |
| **Create an idea** `stormboard_create_an_idea` | Create a new idea in an existing Stormboard storm |
| **Create tag data for an idea** `stormboard_create_tag_data_for_an_idea` | Update tag data for an idea |
| **Decline a storm invite** `stormboard_decline_a_storm_invite` | Decline a Storm invitation and remove it from your list |
| **Duplicate a storm** `stormboard_duplicate_a_storm` | Duplicate an existing Storm |
| **Invite participants** `stormboard_invite_participants` | Invite people to join a Storm by email |
| **Join a storm** `stormboard_join_a_storm` | Join a Storm using its ID and access key |

## Example prompts

**Check Authentication**

> Use Stormboard to check authentication and walk me through the result in plain English.

**Details**

> Use Stormboard to details and walk me through the result in plain English.

**Get A List Of Connectors In A Storm**

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

**Get A List Of Ideas**

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

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use Stormboard
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 Trello integration](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards
- [Hermes Moco integration](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.
- [ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints