# How to connect Parallel to Hermes Agent (paste one key, 32 tools) > Connect Parallel to Hermes with ClawLink: paste your Parallel key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/parallel Most guides for giving Hermes Agent Parallel 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 Parallel setup: pair once in the browser and your always-on Hermes agent can act on Parallel 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 Parallel. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Parallel** — 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 parallel # connect Parallel (browser OAuth) npx -y @useclawlink/cli actions parallel # list available actions npx -y @useclawlink/cli run parallel --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 Parallel in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Parallel API key once. Verify the connection by asking Hermes: > Create it in Parallel for me, then confirm the important fields before you finish. ### 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 Parallel is connected in the dashboard, that agent calls the same 32 Parallel 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). ## Parallel MCP for Hermes Looking for a Parallel MCP server for Hermes Agent? ClawLink connects Parallel to Hermes Agent and exposes 32 Parallel 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 Parallel integration](https://claw-link.dev/openclaw/parallel) works the same way. ## What the Hermes Agent Parallel integration can do 32 Parallel 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 32. ### 30 of 32 Parallel tools for Hermes | Tool | What it does | |---|---| | **Create chat completions** `parallel_create_chat_completions` | Get realtime chat completions from Parallel AI | | **Extract** `parallel_extract` | Extract relevant content from specific web URLs | | **Fetch task group runs** `parallel_fetch_task_group_runs` | Retrieve task runs from a Task Group as a resumable stream | | **Get find all run result** `parallel_get_find_all_run_result` | Fetch the final (or latest available) FindAll candidates and result payload for a run | | **Get find all run schema** `parallel_get_find_all_run_schema` | Retrieve the schema configuration of a FindAll run by findall_id | | **Ingest find all run** `parallel_ingest_find_all_run` | Transform a natural language search objective into a structured FindAll specification | | **List monitor events** `parallel_list_monitor_events` | List events for a monitor from up to the last 300 event groups | | **List monitors** `parallel_list_monitors` | List active monitors for the user | | **Retrieve event group** `parallel_retrieve_event_group` | Retrieve an event group for a monitor | | **Retrieve find all run status** `parallel_retrieve_find_all_run_status` | Retrieve status and metadata for a FindAll run by findall_id | | **Retrieve monitor** `parallel_retrieve_monitor` | Retrieve a specific monitor by ID | | **Retrieve task group** `parallel_retrieve_task_group` | Retrieve details of a specific task group | | **Retrieve task group run** `parallel_retrieve_task_group_run` | Retrieve run status by run_id for a task group | | **Retrieve task run** `parallel_retrieve_task_run` | Retrieve run status by run_id | | **Retrieve task run input** `parallel_retrieve_task_run_input` | Retrieve the input data of a specific task run by run_id | | **Retrieve task run result** `parallel_retrieve_task_run_result` | Retrieve the result of a task run by run_id, blocking until the run completes | | **Search** `parallel_search` | Perform parallel semantic search | | **Stream find all events** `parallel_stream_find_all_events` | Stream events from a FindAll run | | **Stream task group events** `parallel_stream_task_group_events` | Stream events for a Task Group | | **Stream task run events** `parallel_stream_task_run_events` | Stream events for a Task Run | | **Suggest task** `parallel_suggest_task` | Suggest tasks based on user intent | | **Add enrichment to find all run** `parallel_add_enrichment_to_find_all_run` | Add an enrichment to a FindAll run | | **Add runs to task group** `parallel_add_runs_to_task_group` | Initiate multiple task runs within a TaskGroup | | **Create monitor** `parallel_create_monitor` | Create a web monitor that periodically runs the specified query | | **Create task group** `parallel_create_task_group` | Create a new task group | | **Create task run** `parallel_create_task_run` | Create and initiate a task run | | **Extend find all run** `parallel_extend_find_all_run` | Extend a FindAll run by adding additional matches to the current match limit | | **Find all** `parallel_find_all` | Start a FindAll run | | **Simulate event** `parallel_simulate_event` | Simulate sending an event for a monitor | | **Update monitor** `parallel_update_monitor` | Update a monitor's configuration | ## Example prompts **Create Chat Completions** > Create it in Parallel for me, then confirm the important fields before you finish. **Extract** > Use Parallel to extract and walk me through the result in plain English. **Fetch Task Group Runs** > Pull the relevant data from Parallel, summarize it in plain English, and point out anything that needs attention. **Get Find All Run Result** > Pull the relevant data from Parallel, 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 Parallel working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Parallel API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Parallel 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 Parallel. | 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 Parallel actions to the runtime in a format your agent can reliably use. | 32 tools for Parallel are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Parallel 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 Parallel in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the Parallel 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 Parallel 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 Parallel 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 Parallel tools Parallel 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 Parallel 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. ### Parallel 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 Parallel 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 Parallel integration? Yes. ClawLink is the fastest way to connect Hermes to Parallel: link your Parallel account once in the browser and Hermes Agent can call the Parallel API through 32 ready-made tools — no custom code or token handling. ### How do I connect Parallel 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 Parallel in the dashboard and Hermes can use it from the next message — no config files, and the Parallel key you paste is stored server-side instead of in your environment. ### How long does it take to connect Parallel to Hermes Agent? About two minutes. Sign in, click Connect next to Parallel in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Parallel 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 Parallel working from chat. ### Hermes paired but still can't use Parallel 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 DataRobot](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 tools](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. - [Just One API](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.