# How to connect Kintone to OpenClaw (paste one key, 16 tools) > Connect Kintone to OpenClaw with ClawLink: paste your Kintone key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/kintone The usual route to Kintone access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Kintone setup: install one ClawHub skill, connect Kintone in the browser, and OpenClaw can call real Kintone actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Kintone. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Kintone** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 kintone # connect Kintone (browser OAuth) npx -y @useclawlink/cli actions kintone # list available actions npx -y @useclawlink/cli run kintone --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Kintone in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Kintone API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Kintone, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw 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 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Kintone MCP for OpenClaw Looking for a Kintone MCP server for OpenClaw? ClawLink connects Kintone to OpenClaw and exposes 16 Kintone 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 Hermes instead? The [Hermes Kintone integration](https://claw-link.dev/hermes/kintone) works the same way. ## What the OpenClaw Kintone integration can do 16 Kintone tools are ready for OpenClaw 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 OpenClaw | 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 | ## Example prompts **Get User Access** > Pull the relevant data from Kintone, summarize it in plain English, and point out anything that needs attention. **List Directory Containers** > List the relevant items in Kintone, group them by priority, and recommend what OpenClaw should do next. **List Members** > List the relevant items in Kintone, group them by priority, and recommend what OpenClaw should do next. **List Users** > List the relevant items in Kintone, group them by priority, and recommend what OpenClaw 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 OpenClaw. 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Kintone skill but can't call the tools The ClawHub skill teaches OpenClaw about Kintone, but the calls run through the ClawLink plugin and your connected account. Make sure Kintone is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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. ### Is there a OpenClaw Kintone integration? Yes. ClawLink is the fastest way to connect OpenClaw to Kintone: link your Kintone account once in the browser and OpenClaw can call the Kintone API through 16 ready-made tools — no custom code or token handling. ### How do I add Kintone to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Kintone skill from ClawHub, then you click Connect in the dashboard to authorize Kintone. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Kintone in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Kintone working from chat. ### OpenClaw installed the Kintone skill but can't call the tools The ClawHub skill teaches OpenClaw about Kintone, but the calls run through the ClawLink plugin and your connected account. Make sure Kintone is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw Greenhouse integration](https://claw-link.dev/openclaw/greenhouse) — Manage jobs, candidates, applications, and interviews - [OpenClaw Ashby integration](https://claw-link.dev/openclaw/ashby) — 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. - [OpenClaw Lever integration](https://claw-link.dev/openclaw/lever) — Manage candidates, opportunities, interviews, and requisitions