How to connect Yandex to Hermes Agent
Connect Yandex 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.
YandexOAUTH2MCPSearch the web, translate text, and query Yandex services. Once connected, Hermes Agent can read and act on Yandex from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Yandex 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 Yandex setup: pair once in the browser and your always-on Hermes agent can act on Yandex 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.
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 Yandex.
1Install 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 Yandex
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Yandex?"
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 testThen connect Yandex in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Use Yandex to geocoder reverse 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 loginlogin opens the same browser approval and stores a credential locally. Once Yandex is connected in the dashboard, that agent calls the same 21 Yandex tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Yandex MCP for Hermes
Looking for a Yandex MCP server for Hermes Agent? ClawLink connects Yandex to Hermes Agent and exposes 21 Yandex tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Yandex integration works the same way.
What the Hermes Agent Yandex integration can do
21 Yandex tools are ready for Hermes Agent once the account is connected.
All 21 Yandex tools for Hermes
| Tool | What it does |
|---|---|
Geocoder reverse yandex_geocoder_reverse | Tool to convert geographic coordinates to a human-readable address (reverse geocoding). Returns address information including street, city, country, and other location details. |
Get account experiments yandex_get_account_experiments | Tool to retrieve Yandex Music account experimental features and A/B testing flags. Use when you need to check which experimental features are enabled for an account. |
Get account status yandex_get_account_status | Tool to retrieve Yandex Music account status and permissions. Use when you need to check account availability, region, subscription status, and granted permissions. |
Get genres yandex_get_genres | Tool to retrieve the list of music genres from Yandex Music. Use when you need to get available music genres for browsing or categorization. |
Get permission alerts yandex_get_permission_alerts | Tool to retrieve permission alerts and notifications from Yandex Music API. Use this to check for system notifications about subscription status, permissions, or other user alerts. |
Get playlists IDS by tag yandex_get_playlists_ids_by_tag | Tool to retrieve playlist IDs associated with a specific tag. Use when you need to find playlists categorized under a tag like 'rock', 'pop', or 'jazz'. |
Get public resource yandex_get_public_resource | Tool to retrieve metadata for a public file or folder on Yandex Disk. Use when you need to get information about publicly shared resources including their properties, nested items, and download URLs. |
Get public resource download link yandex_get_public_resource_download_link | Tool to get a direct download link for a publicly shared Yandex Disk resource. Use when you need to download a file or folder that has been shared publicly. |
Get rotor account status yandex_get_rotor_account_status | Tool to retrieve authenticated user's rotor account status with supplementary fields. Use to check user subscription status, permissions, and radio-specific settings like skips_per_hour. |
Get rotor stations dashboard yandex_get_rotor_stations_dashboard | Tool to retrieve recommended radio stations for the current user. Use when you need to get the user's personalized station dashboard. |
Get settings yandex_get_settings | Tool to retrieve Yandex Music settings including available purchase products and payment configuration. Use when you need to check available subscription options, pricing, or payment methods. |
Get stations list yandex_get_stations_list | Tool to retrieve all radio stations with user settings from Yandex Music. Use when you need to get the list of available radio stations and their configurations. |
Get track download info yandex_get_track_download_info | Retrieve available download options for a Yandex Music track |
List filters yandex_list_filters | Retrieve all filters configured for a Yandex Metrica counter |
List goals yandex_list_goals | Retrieve all goals configured for a Yandex Metrica counter |
List grants yandex_list_grants | Retrieve the list of permissions (grants) for a Yandex Metrica counter |
List log requests yandex_list_log_requests | Retrieve a list of log requests for a Yandex Metrica counter |
List storage buckets yandex_list_storage_buckets | List all Yandex Object Storage buckets owned by the authenticated user |
Organization search yandex_organization_search | Find businesses and organizations by name, address, or TIN |
Route yandex_route | Generate detailed route for driving, walking, or public transport |
Tiles yandex_tiles | Fetch individual map tile images by x/y coordinates and zoom level |
Try it: find the Yandex tool you need
Browse the 21 Yandex tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Yandex to geocoder reverse and walk me through the result in plain English.
Pull the relevant data from Yandex, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Yandex, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Yandex, summarize it in plain English, and point out anything that needs attention.
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 Yandex working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Yandex app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Yandex 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 Yandex. | 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 Yandex actions to the runtime in a format your agent can reliably use. | 21 tools for Yandex are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Yandex 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 Yandex 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 comparison.
Troubleshooting
Hermes paired but still can't use Yandex
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 Yandex 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 Yandex tools
Yandex 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 Yandex 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.
Yandex 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 Yandex 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 Yandex integration?
Yes. ClawLink is the fastest way to connect Hermes to Yandex: link your Yandex account once in the browser and Hermes Agent can call the Yandex API through 21 ready-made tools — no custom code or token handling.
How do I connect Yandex 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 Yandex 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 Yandex to Hermes Agent?
About two minutes. Sign in, click Connect next to Yandex in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Yandex 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 Yandex working from chat.
Hermes paired but still can't use Yandex
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.
