How to connect Leiga to Hermes Agent
Connect Leiga to Hermes with ClawLink: paste your Leiga key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
LeigaAPI KEYMCPLeiga is an AI-powered project management tool that automates tasks and enhances team collaboration.. Once connected, Hermes Agent can read and act on Leiga from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Leiga 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 Leiga setup: pair once in the browser and your always-on Hermes agent can act on Leiga 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 Leiga.
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 Leiga
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Leiga?"
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 Leiga in the ClawLink dashboard — paste your Leiga API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Leiga, summarize it in plain English, and point out anything that needs attention.
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 Leiga is connected in the dashboard, that agent calls the same 10 Leiga tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Leiga MCP for Hermes
Looking for a Leiga MCP server for Hermes Agent? ClawLink connects Leiga to Hermes Agent and exposes 10 Leiga tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Leiga integration works the same way.
What the Hermes Agent Leiga integration can do
10 Leiga tools are ready for Hermes Agent once the account is connected.
All 10 Leiga tools for Hermes
| Tool | What it does |
|---|---|
Get file list leiga_get_file_list | Retrieve a paginated list of files in a specified directory |
Get issue detail by issue number leiga_get_issue_detail_by_issue_number | Fetch detailed information about a specific issue using its issue number |
Get issue schema leiga_get_issue_schema | Retrieve the issue custom-field schema |
Get project information leiga_get_project_information | Fetch detailed information about a specific project by its ID |
Get project overview template leiga_get_project_overview_template | Retrieve the project overview template |
Get project template list leiga_get_project_template_list | Retrieve a list of project templates |
Get version list leiga_get_version_list | Fetch list of versions for a specific platform |
Get webhook type list leiga_get_webhook_type_list | Retrieve the list of available webhook types |
List projects leiga_list_projects | List all projects available to the authenticated user |
Create project leiga_create_project | Create a new project in Leiga |
Try it: find the Leiga tool you need
Browse the 10 Leiga tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Leiga, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Leiga, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Leiga, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Leiga, 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 Leiga working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Leiga API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Leiga 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 Leiga. | 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 Leiga actions to the runtime in a format your agent can reliably use. | 10 tools for Leiga are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Leiga 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 Leiga in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Leiga key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Leiga
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 Leiga 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 Leiga tools
Leiga 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 Leiga 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.
Leiga 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 Leiga has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Leiga integration?
Yes. ClawLink is the fastest way to connect Hermes to Leiga: link your Leiga account once in the browser and Hermes Agent can call the Leiga API through 10 ready-made tools — no custom code or token handling.
How do I connect Leiga 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 Leiga in the dashboard and Hermes can use it from the next message — no config files, and the Leiga key you paste is stored server-side instead of in your environment.
How long does it take to connect Leiga to Hermes Agent?
About two minutes. Sign in, click Connect next to Leiga in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Leiga 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 Leiga working from chat.
Hermes paired but still can't use Leiga
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.
