How to connect Kintone to Hermes Agent
Connect Kintone to Hermes with ClawLink: paste your Kintone key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.


Manage users, departments, groups, memberships, service assignments, and login codes in a Kintone tenant through the User API.. Once connected, Hermes Agent can read and act on Kintone from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Kintone 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 Kintone setup: pair once in the browser and your always-on Hermes agent can act on Kintone 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 Kintone.
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 Kintone
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Kintone?"
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 Kintone in the ClawLink dashboard — paste your Kintone API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Kintone, 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 Kintone is connected in the dashboard, that agent calls the same 16 Kintone tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Kintone MCP for Hermes
Looking for a Kintone MCP server for Hermes Agent? ClawLink connects Kintone to Hermes Agent and exposes 16 Kintone tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Kintone integration works the same way.
What the Hermes Agent Kintone integration can do
16 Kintone tools are ready for Hermes Agent once the account is connected. The 15 below are the ones people reach for most; your agent can call all 16.
15 of 16 Kintone tools for Hermes
| Tool | What it does |
|---|---|
Get user access kintone_get_user_access | Get one user's department memberships, group memberships, and Kintone service assignment in one |
List directory containers kintone_list_directory_containers | List or filter Kintone departments or groups, one page at a time |
List members kintone_list_members | List users belonging to a Kintone department or group, one page at a time |
List users kintone_list_users | List or filter tenant users by ID or login code, one page at a time |
Create departments kintone_create_departments | Create 1 to 100 Kintone departments in one batch |
Create groups kintone_create_groups | Create 1 to 100 static or dynamic Kintone groups in one batch |
Create users kintone_create_users | Create 1 to 100 Kintone tenant users in one batch with a login code, password, and display name |
Update departments kintone_update_departments | Update mutable fields for 1 to 100 existing Kintone departments, identified by exact department |
Update groups kintone_update_groups | Update the name and optional description of 1 to 100 existing Kintone groups, identified by |
Update users kintone_update_users | Update editable profile and primary-organization fields for 1 to 100 existing Kintone tenant |
Change login codes kintone_change_login_codes | Irreversibly change the login codes of up to 100 Kintone users in one batch |
Replace group users kintone_replace_group_users | Replace a Kintone static group's complete user membership list |
Replace user departments kintone_replace_user_departments | Replace the complete department membership lists for one to 100 Kintone users |
Replace user groups kintone_replace_user_groups | Replace a Kintone user's complete static-group membership list |
Set service assignments kintone_set_service_assignments | Replace Kintone service access for one to 100 users |
Try it: find the Kintone tool you need
Browse the 15 Kintone 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 Kintone, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Kintone, group them by priority, and recommend what Hermes should do next.
List the relevant items in Kintone, group them by priority, and recommend what Hermes should do next.
List the relevant items in Kintone, group them by priority, and recommend what Hermes should do next.
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 Kintone working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Kintone API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Kintone 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 Kintone. | 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 Kintone actions to the runtime in a format your agent can reliably use. | 16 tools for Kintone are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Kintone 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 Kintone in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Kintone 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 Kintone
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 Kintone 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 Kintone tools
Kintone 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 Kintone 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.
Kintone 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 Kintone 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 Kintone integration?
Yes. ClawLink is the fastest way to connect Hermes to Kintone: link your Kintone account once in the browser and Hermes Agent can call the Kintone API through 16 ready-made tools — no custom code or token handling.
How do I connect Kintone 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 Kintone in the dashboard and Hermes can use it from the next message — no config files, and the Kintone key you paste is stored server-side instead of in your environment.
How long does it take to connect Kintone to Hermes Agent?
About two minutes. Sign in, click Connect next to Kintone in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Kintone 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 Kintone working from chat.
Hermes paired but still can't use Kintone
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
Greenhouse
Manage jobs, candidates, applications, and interviews
Ashby tools
Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process.
Lever tools
Manage candidates, opportunities, interviews, and requisitions