# How to connect Era Context to Hermes Agent (no API keys)

> Connect Era Context to Hermes with ClawLink in one click — 50 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Web version: https://claw-link.dev/hermes/era-context

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

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Era Context** — 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 era-context  # connect Era Context (browser OAuth)
npx -y @useclawlink/cli actions era-context  # list available actions
npx -y @useclawlink/cli run era-context <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 Era Context in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys.

Verify the connection by asking Hermes:

> Use Era Context to mcp accounts check account balance 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 Era Context is connected in the dashboard, that agent calls the same 50 Era Context 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).

## Era Context MCP for Hermes

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

## What the Hermes Agent Era Context integration can do

50 Era Context 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 50.

### 30 of 50 Era Context tools for Hermes

| Tool | What it does |
|---|---|
| **Mcp accounts check account balance** `era_context_mcp_accounts__check_account_balance` | Get the current and available balance for a specific account, including credit limit if |
| **Mcp accounts list financial accounts** `era_context_mcp_accounts__list_financial_accounts` | List all linked bank accounts, credit cards, and investment accounts with current and available |
| **Mcp billing get current plan** `era_context_mcp_billing__get_current_plan` | Get the user's current subscription plan, tier, usage against meter limits, and what the next |
| **Mcp billing list payments** `era_context_mcp_billing__list_payments` | List the user's past invoices — what they were charged, when, for which service period, and |
| **Mcp billing list plans** `era_context_mcp_billing__list_plans` | List all available subscription plans with pricing, billing periods, feature comparisons |
| **Mcp billing list subscriptions** `era_context_mcp_billing__list_subscriptions` | List what the user is actually being charged for right now, read live from Stripe, broken down |
| **Mcp connections list connections** `era_context_mcp_connections__list_connections` | List every one of the user's connections with an honest, provider-agnostic status for each: |
| **Mcp help get help** `era_context_mcp_help__get_help` | Get contextual help and onboarding guidance for Era Context |
| **Mcp insights analyze spending** `era_context_mcp_insights__analyze_spending` | Break down spending by category, merchant, account, week, or month |
| **Mcp insights compare spending periods** `era_context_mcp_insights__compare_spending_periods` | Compare spending between any two time periods side-by-side with pre-computed deltas and |
| **Mcp insights forecast spending** `era_context_mcp_insights__forecast_spending` | Estimate how much the user will spend by the end of the current period based on their spending |
| **Mcp insights get cash flow** `era_context_mcp_insights__get_cash_flow` | Analyze income, spending, and net cash flow over multiple weeks or months (up to 12 periods) |
| **Mcp insights get daily category spending** `era_context_mcp_insights__get_daily_category_spending` | Get a per-day, per-category spending breakdown for a calendar month |
| **Mcp insights get daily financial summary** `era_context_mcp_insights__get_daily_financial_summary` | Get daily financial calendar for a month |
| **Mcp knowledge get financial context and overview** `era_context_mcp_knowledge__get_financial_context_and_overview` | Load the user's profile, complete financial snapshot (all account balances, net worth, this |
| **Mcp knowledge get pending questions** `era_context_mcp_knowledge__get_pending_questions` | Get the next onboarding questions to ask the user |
| **Mcp knowledge recall history** `era_context_mcp_knowledge__recall_history` | Get the version history of a specific fact about the user |
| **Mcp knowledge show question ui** `era_context_mcp_knowledge__show_question_ui` | Present an onboarding question using a visual input control (slider, date picker, multi-select |
| **Mcp nurture get my status** `era_context_mcp_nurture__get_my_status` | Get the caller's own nurture (lifecycle email) campaign enrollment status — which campaigns |
| **Mcp referral get dashboard sso** `era_context_mcp_referral__get_dashboard_sso` | Get a single-use SSO magic link to open the user's Rewardful affiliate dashboard |
| **Mcp referral get referral link** `era_context_mcp_referral__get_referral_link` | Get the user's referral link if they are enrolled in the referral program |
| **Mcp referral get referral stats** `era_context_mcp_referral__get_referral_stats` | Get the user's referral performance statistics: visitors, conversions, earned commissions, and |
| **Mcp transactions list recurring charges** `era_context_mcp_transactions__list_recurring_charges` | List detected recurring transactions — subscriptions (Netflix, Spotify), bills (rent |
| **Mcp transactions list spending categories** `era_context_mcp_transactions__list_spending_categories` | List all available spending categories organized in a parent/child hierarchy (e.g., 'Daily |
| **Mcp transactions list transactions** `era_context_mcp_transactions__list_transactions` | List recent transactions with pagination, optionally filtered by account and date range |
| **Mcp transactions search transactions** `era_context_mcp_transactions__search_transactions` | Search and filter transactions by merchant name, description, amount range, date range, and |
| **Mcp accounts set account visibility** `era_context_mcp_accounts__set_account_visibility` | Set the visibility of a single financial account |
| **Mcp accounts toggle balance backfill** `era_context_mcp_accounts__toggle_balance_backfill` | Toggle balance backfill for an account group |
| **Mcp billing cancel subscription** `era_context_mcp_billing__cancel_subscription` | Initiate subscription cancellation |
| **Mcp billing uncancel subscription** `era_context_mcp_billing__uncancel_subscription` | Un-cancel a subscription that Stripe holds a scheduled cancellation for, in either of the two |

## Example prompts

**Mcp Accounts Check Account Balance**

> Use Era Context to mcp accounts check account balance and walk me through the result in plain English.

**Mcp Accounts List Financial Accounts**

> Use Era Context to mcp accounts list financial accounts and walk me through the result in plain English.

**Mcp Billing Get Current Plan**

> Use Era Context to mcp billing get current plan and walk me through the result in plain English.

**Mcp Billing List Payments**

> Use Era Context to mcp billing list payments 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 Era Context working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a Era Context app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Era Context 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 Era Context. | 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 Era Context actions to the runtime in a format your agent can reliably use. | 50 tools for Era Context are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Era Context 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 Era Context in the browser, and the 50 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](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Era Context
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 Era Context 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 Era Context tools
Era Context 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 Era Context 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.

### Era Context 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 Era Context and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

### Is there a Hermes Agent Era Context integration?
Yes. ClawLink is the fastest way to connect Hermes to Era Context: link your Era Context account once in the browser and Hermes Agent can call the Era Context API through 50 ready-made tools — no custom code or token handling.

### How do I connect Era Context 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 Era Context 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 Era Context to Hermes Agent?
About two minutes. Sign in, click Connect next to Era Context in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Era Context up myself?
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 Era Context working from chat.

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

- [PostHog](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags
- [DataforSEO tools](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits
- [Metabase](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.