How to connect Clarify to Hermes Agent (no API keys)

Most guides for giving Hermes Agent Clarify 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 Clarify setup: pair once in the browser and your always-on Hermes agent can act on Clarify for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Copy this prompt into Hermes to install the plugin and pair your account.

Prompt for Hermes

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. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin

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.

Setup

It takes three steps to connect Hermes to Clarify.

1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2
Connect Clarify
One-click OAuth in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Clarify?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

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 Clarify in the ClawLink dashboard — a one-click OAuth approval, no API keys.

Verify the connection by asking Hermes:

Use Clarify to mcp find leads 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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Clarify is connected in the dashboard, that agent calls the same 46 Clarify tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Clarify MCP for Hermes

Looking for a Clarify MCP server for Hermes Agent? ClawLink connects Clarify to Hermes Agent and exposes 46 Clarify tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Clarify integration works the same way.

What the Hermes Agent Clarify integration can do

46 Clarify 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 46.

30 of 46 Clarify tools for Hermes

Tool	What it does
Mcp find leads `clarify_mcp_find_leads`	Search Clarify's built-in prospect database of companies and people to find new leads matching
Mcp get agent runs `clarify_mcp_get_agent_runs`	List an agent's runs, executions, invocations, and past run history, or fetch one run with its
Mcp get agents `clarify_mcp_get_agents`	List agents visible to the current user, or fetch a single agent by ID
Mcp get artifact component doc `clarify_mcp_get_artifact_component_doc`	Get the full prop contract for one or more Clarify design-system components available to
Mcp get artifact source `clarify_mcp_get_artifact_source`	Read the current source of an existing artifact — the JSX of its applied version, plus its name
Mcp get calendar events `clarify_mcp_get_calendar_events`	List the current user's calendar events in a time range
Mcp get campaign recipients `clarify_mcp_get_campaign_recipients`	List the individual people enrolled in a campaign, with their per-person engagement — who
Mcp get campaigns `clarify_mcp_get_campaigns`	List campaigns in the workspace, or fetch a single campaign by ID with full details
Mcp get current user `clarify_mcp_get_current_user`	Get information about the current authenticated user, including their timezone
Mcp get lists `clarify_mcp_get_lists`	Get list metadata (saved views) for an entity type, or fetch a single list by ID
Mcp get records `clarify_mcp_get_records`	Retrieve detailed information about specific records by their IDs
Mcp get schema `clarify_mcp_get_schema`	Get the schema for Clarify entities
Mcp get workflow runs `clarify_mcp_get_workflow_runs`	Get execution runs for a workflow
Mcp get workflows `clarify_mcp_get_workflows`	Get and search workflows in the workspace, or fetch a single workflow with its full
Mcp query analytics `clarify_mcp_query_analytics`	Execute read-only ClickHouse SQL against the analytics event log
Mcp query data `clarify_mcp_query_data`	Execute PostgreSQL queries to retrieve data from Clarify
Mcp read context `clarify_mcp_read_context`	Read Clarify product knowledge and documentation
Mcp add comment `clarify_mcp_add_comment`	Add a comment to a supported entity
Mcp create campaign `clarify_mcp_create_campaign`	Create a new email campaign (sequence) in DRAFT mode
Mcp create email draft `clarify_mcp_create_email_draft`	Create an email draft in the user's connected Gmail or Outlook account for them to review
Mcp import leads `clarify_mcp_import_leads`	Import leads from a tam_company or tam_person search into Clarify
Mcp import meeting transcript `clarify_mcp_import_meeting_transcript`	Import a meeting transcript from an external source (Granola, Notion, Circleback)
Mcp respond to calendar event `clarify_mcp_respond_to_calendar_event`	RSVP to a calendar event you've been invited to
Mcp send email `clarify_mcp_send_email`	Send an email immediately through the user's connected email account
Mcp submit feedback `clarify_mcp_submit_feedback`	Submit concise feature requests or feedback about MCP tools
Mcp create or update agent `clarify_mcp_create_or_update_agent`	Create or update an agent, an autonomous AI assistant
Mcp create or update artifact `clarify_mcp_create_or_update_artifact`	Create a new artifact or write a new version to an existing artifact
Mcp create or update calendar event `clarify_mcp_create_or_update_calendar_event`	Create a new calendar event or update an existing one
Mcp create or update custom object `clarify_mcp_create_or_update_custom_object`	Create a new custom object type or update an existing one in the workspace
Mcp create or update fields `clarify_mcp_create_or_update_fields`	Create new fields or update existing field metadata (name, options, AI config) on any entity

Try it: find the Clarify tool you need

Browse the 30 Clarify tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Use Clarify to mcp find leads and walk me through the result in plain English.

Use Clarify to mcp get agent runs and walk me through the result in plain English.

Use Clarify to mcp get agents and walk me through the result in plain English.

Use Clarify to mcp get artifact component doc and walk me through the result in plain English.

ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app 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 Clarify working from chat.

	Manual	ClawLink
Connection flow	Register a Clarify app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift.	Users connect Clarify through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code.
Ongoing maintenance	You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Clarify.	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 Clarify actions to the runtime in a format your agent can reliably use.	46 tools for Clarify are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Clarify 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 Clarify in the browser, and the 46 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use Clarify

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 Clarify 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 Clarify tools

Clarify 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 Clarify 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.

Clarify 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.

OAuth finished in the browser but the account is still missing

Try reconnecting Clarify and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

FAQ

Is there a Hermes Agent Clarify integration?

Yes. ClawLink is the fastest way to connect Hermes to Clarify: link your Clarify account once in the browser and Hermes Agent can call the Clarify API through 46 ready-made tools — no custom code or token handling.

How do I connect Clarify 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 Clarify in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

How long does it take to connect Clarify to Hermes Agent?

About two minutes. Sign in, click Connect next to Clarify in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Clarify up myself?

Hermes paired but still can't use Clarify

How to connect Clarify to Hermes Agent

Setup

Install and pair

Connect Clarify

Use it from chat