# How to connect Mighty Networks to Hermes Agent (paste one key, 24 tools) > Connect Mighty Networks to Hermes with ClawLink: paste your Mighty Networks key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/mighty-networks Most guides for giving Hermes Agent Mighty Networks 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 Mighty Networks setup: pair once in the browser and your always-on Hermes agent can act on Mighty Networks 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 Mighty Networks. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Mighty Networks** — 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 mighty-networks # connect Mighty Networks (browser OAuth) npx -y @useclawlink/cli actions mighty-networks # list available actions npx -y @useclawlink/cli run mighty-networks --input '' # 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 Mighty Networks in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Mighty Networks API key once. Verify the connection by asking Hermes: > Pull the relevant data from Mighty Networks, 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 Mighty Networks is connected in the dashboard, that agent calls the same 24 Mighty Networks 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). ## Mighty Networks MCP for Hermes Looking for a Mighty Networks MCP server for Hermes Agent? ClawLink connects Mighty Networks to Hermes Agent and exposes 24 Mighty Networks 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 Mighty Networks integration](https://claw-link.dev/openclaw/mighty-networks) works the same way. ## What the Hermes Agent Mighty Networks integration can do 24 Mighty Networks tools are ready for Hermes Agent once the account is connected. The 23 below are the ones people reach for most; your agent can call all 24. ### 23 of 24 Mighty Networks tools for Hermes | Tool | What it does | |---|---| | **Get event** `mighty_networks_get_event` | Return details for one Mighty Networks event by ID | | **Get member** `mighty_networks_get_member` | Return one member in the connected Mighty Network by member ID or exact email address | | **Get network** `mighty_networks_get_network` | Return identity and profile details for the Network connected to this Admin API key | | **Get post** `mighty_networks_get_post` | Return details for one Mighty Networks post or article by ID | | **Get space** `mighty_networks_get_space` | Return details for one space in the connected Mighty Network by ID | | **List abuse reports** `mighty_networks_list_abuse_reports` | Return one page of abuse reports for moderation review | | **List collections** `mighty_networks_list_collections` | Return one page of collections that organize spaces in the connected Mighty Network | | **List event rsvps** `mighty_networks_list_event_rsvps` | Return one page of RSVP records for an event in the connected Mighty Network | | **List events** `mighty_networks_list_events` | Return one page of events in the connected Mighty Network | | **List invites** `mighty_networks_list_invites` | Return one page of Network invitations, optionally filtered by recipient email | | **List members** `mighty_networks_list_members` | Return one page of members in the connected Mighty Network | | **List plans** `mighty_networks_list_plans` | Return one page of access and payment plans configured for the connected Mighty Network | | **List posts** `mighty_networks_list_posts` | Return one page of posts across the connected Mighty Network | | **List spaces** `mighty_networks_list_spaces` | Return one page of spaces in the connected Mighty Network | | **Add member to space** `mighty_networks_add_member_to_space` | Add an existing member of the connected Mighty Network to a space, granting that member access | | **Create event** `mighty_networks_create_event` | Create a one-time or recurring visible event in a Mighty Networks space | | **Create invite** `mighty_networks_create_invite` | Create an invitation to the connected Mighty Network | | **Create member** `mighty_networks_create_member` | Create a full Network member or a limited member assigned to specified spaces | | **Create post** `mighty_networks_create_post` | Create and publish a visible post or article in a Mighty Networks space | | **Set event rsvp** `mighty_networks_set_event_rsvp` | Create or update a Mighty Networks member's RSVP for an event | | **Update member** `mighty_networks_update_member` | Update selected profile or Network role fields for an existing member | | **Revoke invite** `mighty_networks_revoke_invite` | Revoke an unaccepted invitation to the connected Mighty Network | | **Update post** `mighty_networks_update_post` | Update the title and/or body of an existing Mighty Networks post or article; provide at least | ## Example prompts **Get Event** > Pull the relevant data from Mighty Networks, summarize it in plain English, and point out anything that needs attention. **Get Member** > Pull the relevant data from Mighty Networks, summarize it in plain English, and point out anything that needs attention. **Get Network** > Pull the relevant data from Mighty Networks, summarize it in plain English, and point out anything that needs attention. **Get Post** > Pull the relevant data from Mighty Networks, 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 Mighty Networks working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Mighty Networks API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mighty Networks 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 Mighty Networks. | 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 Mighty Networks actions to the runtime in a format your agent can reliably use. | 24 tools for Mighty Networks are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Mighty Networks 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 Mighty Networks in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Mighty Networks 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 Mighty Networks 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 Mighty Networks 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 Mighty Networks tools Mighty Networks 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 Mighty Networks 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. ### Mighty Networks 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 Mighty Networks 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 Mighty Networks integration? Yes. ClawLink is the fastest way to connect Hermes to Mighty Networks: link your Mighty Networks account once in the browser and Hermes Agent can call the Mighty Networks API through 24 ready-made tools — no custom code or token handling. ### How do I connect Mighty Networks 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 Mighty Networks in the dashboard and Hermes can use it from the next message — no config files, and the Mighty Networks key you paste is stored server-side instead of in your environment. ### How long does it take to connect Mighty Networks to Hermes Agent? About two minutes. Sign in, click Connect next to Mighty Networks in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Mighty Networks 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 Mighty Networks working from chat. ### Hermes paired but still can't use Mighty Networks 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 GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.