# How to connect Stytch to Hermes Agent (no API keys) > Connect Stytch to Hermes with ClawLink in one click — 21 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/stytch Most guides for giving Hermes Agent Stytch 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 Stytch setup: pair once in the browser and your always-on Hermes agent can act on Stytch 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 Stytch. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Stytch** — 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 stytch # connect Stytch (browser OAuth) npx -y @useclawlink/cli actions stytch # list available actions npx -y @useclawlink/cli run stytch --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 Stytch in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Stytch to mcp get all email templates 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 Stytch is connected in the dashboard, that agent calls the same 21 Stytch 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). ## Stytch MCP for Hermes Looking for a Stytch MCP server for Hermes Agent? ClawLink connects Stytch to Hermes Agent and exposes 21 Stytch 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 Stytch integration](https://claw-link.dev/openclaw/stytch) works the same way. ## What the Hermes Agent Stytch integration can do 21 Stytch tools are ready for Hermes Agent once the account is connected. The 17 below are the ones people reach for most; your agent can call all 21. ### 17 of 21 Stytch tools for Hermes | Tool | What it does | |---|---| | **Mcp get all email templates** `stytch_mcp_get_all_email_templates` | Retrieve all email templates for a project | | **Mcp get all public tokens** `stytch_mcp_get_all_public_tokens` | Retrieve all active public tokens for a project | | **Mcp get all redirect ur ls** `stytch_mcp_get_all_redirect_ur_ls` | Retrieve all redirect URLs for a project | | **Mcp get b2 bsdk config** `stytch_mcp_get_b2_bsdk_config` | Retrieves the SDK Configuration for a B2B project | | **Mcp get consumer sdk config** `stytch_mcp_get_consumer_sdk_config` | Retrieves the SDK Configuration for a Consumer project | | **Mcp get password strength config** `stytch_mcp_get_password_strength_config` | Retrieve the password strength configuration for a project | | **Mcp list projects** `stytch_mcp_list_projects` | List all Stytch Projects | | **Mcp create email template** `stytch_mcp_create_email_template` | Creates an custom email template for the project | | **Mcp create project** `stytch_mcp_create_project` | Create new Stytch Project | | **Mcp create public token** `stytch_mcp_create_public_token` | Creates a public token for a project | | **Mcp create redirect URL** `stytch_mcp_create_redirect_url` | Create a redirect URL for your project | | **Mcp create secret** `stytch_mcp_create_secret` | Create a new secret for a project | | **Mcp set password strength config** `stytch_mcp_set_password_strength_config` | Set the password strength configuration for a project | | **Mcp update b2 bsdk config** `stytch_mcp_update_b2_bsdk_config` | Updates the SDK Configuration for a B2B project | | **Mcp update consumer sdk config** `stytch_mcp_update_consumer_sdk_config` | Updates the SDK Configuration for a Consumer project | | **Mcp update email template** `stytch_mcp_update_email_template` | Update an email template for a project | | **Mcp update redirect URL** `stytch_mcp_update_redirect_url` | Update valid types for a redirect URL for a project | ## Example prompts **Mcp Get All Email Templates** > Use Stytch to mcp get all email templates and walk me through the result in plain English. **Mcp Get All Public Tokens** > Use Stytch to mcp get all public tokens and walk me through the result in plain English. **Mcp Get All Redirect Ur Ls** > Use Stytch to mcp get all redirect ur ls and walk me through the result in plain English. **Mcp Get B2 Bsdk Config** > Use Stytch to mcp get b2 bsdk config 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 Stytch working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Stytch app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Stytch 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 Stytch. | 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 Stytch actions to the runtime in a format your agent can reliably use. | 21 tools for Stytch are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Stytch 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 Stytch in the browser, and the 21 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 Stytch 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 Stytch 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 Stytch tools Stytch 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 Stytch 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. ### Stytch 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 Stytch 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 Stytch integration? Yes. ClawLink is the fastest way to connect Hermes to Stytch: link your Stytch account once in the browser and Hermes Agent can call the Stytch API through 21 ready-made tools — no custom code or token handling. ### How do I connect Stytch 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 Stytch 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 Stytch to Hermes Agent? About two minutes. Sign in, click Connect next to Stytch in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Stytch 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 Stytch working from chat. ### Hermes paired but still can't use Stytch 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 - [GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [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.