Productivity & Project Management · Kintone + Claude
Kintone MCP with Claude: Automate Team Apps and User Administration
The short answer
Claude connects to Kintone through the Model Context Protocol, a secure standard that lets Claude read and act within the app with permissions you control. Teams can then manage users, update departments, assign groups and create login codes using natural language, while people approve consequential changes before they take effect.
What is Kintone?
Kintone is Cybozu's low-code business app platform. Teams use it to build shared databases, workflows and custom apps for tasks such as customer tracking, project logs, approvals and internal requests, without heavy custom development. Administrators typically manage who can access which apps, how departments are structured and which groups hold which permissions. Because it centralises work data and processes, it is a common home for everyday team operations.
How Claude connects to Kintone through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a tool like Kintone. It defines how Claude asks for information and how it requests actions, so the connection is structured rather than improvised.
Once connected through the Kintone MCP server or a direct API connection, Claude can typically read app records, look up users and departments, and carry out administrative tasks such as updating a department or assigning a user to a group. An administrator can ask in plain English, for example to move three new staff into the Sales group, and Claude works out the steps.
Access is governed by the permissions the organisation sets. Connections use an API key with least-privilege access, so Claude only reaches what it needs. Consequential actions such as removing users or changing permissions can require a named person to approve them, and audit logs record what was done and by whom.
What you can automate
Onboarding new starters
When a new employee joins, an HR or office manager can ask Claude to create their Kintone account, place them in the right department and assign the groups their role needs. Claude carries out the steps and reports back, so the new starter has access on day one without a series of manual admin screens.
Reorganising departments
When a team restructures, administrators often need to move many users at once. Claude can help update department assignments and group memberships in one request, with a summary of changes shown for approval before anything is committed. This reduces errors that come from editing users one by one.
Offboarding and access reviews
Leavers and role changes are a common security gap. Claude can list users in a group, flag accounts that no longer match current roles and prepare removals for approval. Regular access reviews become a routine task rather than a quarterly scramble.
Issuing login codes for field teams
Teams that work away from a desk, such as site staff or temporary contractors, may need login codes issued quickly. Claude can create these on request and log the action, so coordinators can respond to a request in minutes instead of waiting for an administrator to become free.
Answering team questions about app data
Project managers often need a quick view of records, such as open tasks in a project app. Claude can retrieve and summarise relevant records in plain language, helping managers prepare a weekly status note without building reports by hand.
An end-to-end workflow: New hire provisioning across Kintone and Microsoft 365
TriggerAn approved new-starter request is logged in the HR ticketing system.
Claude reads the request and confirms the employee's department, role and start date.
Claude checks Kintone for an existing account to avoid duplicates.
Claude creates the user, assigns the department and adds the role-based groups, then drafts the change summary.
A department head approves the change in the workflow before it is finalised.
Claude records the completed steps in the audit log and posts a confirmation to the Microsoft 365 Teams channel for the onboarding team.
The new starter receives login details through the agreed secure channel.
OutcomeTypical result: provisioning that once took a morning of manual admin is completed in minutes, with fewer missed group assignments and a clear record of each approval.
How we set it up
Free automation audit
We review how your teams use Kintone today and identify the user administration and app workflows worth automating, at no cost and with no obligation.
Secure connection
We connect Claude to Kintone using an API key with least-privilege access, through the Kintone MCP server or a direct API connection, depending on what suits your environment.
Workflow design
We design the end-to-end process across Kintone and your other systems, such as Microsoft 365, CRM or ticketing, and agree which actions need human approval.
Testing against real cases
We test the workflow using past requests and real scenarios, checking accuracy and adjusting permissions before anything goes live.
Launch and team training
We launch with monitoring and audit logs in place, then train administrators and team leads so they can use the workflow confidently and handle exceptions.
Who benefits
- HR and people operations
- Faster, more consistent onboarding and offboarding with fewer manual admin steps.
- IT and system administrators
- Controlled user management with approvals and audit logs, reducing routine workload.
- Department heads and team leads
- Quicker reorganisations and access changes, with clear visibility of what changed.
- Project and operations managers
- Plain-language access to app data for status updates without building reports by hand.
Security and control
- Least-privilege API key access so Claude reaches only the apps and admin functions it needs.
- Human approval required for consequential actions such as removing users or changing permissions.
- Audit logs recording every action Claude takes, with the requester and approver noted.
- Regular access reviews and a documented process for revoking the API key if needed.
- Testing in a non-production environment before any change reaches live user data.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can have Claude workflows designed to align with their privacy and security requirements, including data handling and access controls. In India, workflows can be designed in line with the Digital Personal Data Protection Act, 2023. For organisations in the Middle East, including the UAE and Saudi Arabia, we design around local data protection laws. Hosting region is chosen to meet your specific requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Kintone MCP server do?
The Kintone MCP server is a secure bridge that lets AI tools such as Claude interact with your Kintone environment. It allows approved requests, such as looking up users, updating departments or assigning groups, to be made in plain language. The server acts only within the permissions you configure, so the tool's capabilities stay under your control.
Is connecting Claude to Kintone secure?
Security depends on how the connection is designed. We use an API key with least-privilege access, limit the actions Claude can take, require approval for consequential changes and keep audit logs of all activity. Regular reviews and the ability to revoke the key further reduce risk.
What can Claude do with Kintone once connected?
Typically Claude can read records, look up users and departments, and carry out administrative tasks such as updating departments, assigning groups and creating login codes. The exact actions available depend on the permissions you grant and the workflow we design together.
How long does setup take?
Many projects move from the free audit to launch in a few weeks, though timing depends on how many workflows are in scope and how complex your existing systems are. A simple user administration workflow can often be live sooner than a larger, multi-system process.
Which plan or permissions do I need?
Generally, you need administrator-level access to the Kintone environment to create the API key and grant the required permissions. The exact requirements depend on your Kintone setup and the actions you want to automate, which we confirm during the free audit.