get_recordLABSCO SUMMARY
It can build the app, which is where the caution belongs.
Most kintone integrations read and write records. This one also creates apps, rewrites form layouts, changes access control and deploys to production — so the account you give it should be the account you would give a person with those powers. Two practical notes from the README itself: file downloads at 1MB or above may fail in the current implementation, and the desktop-extension install lets you disable individual tools, which is the easiest way to narrow the surface.
What it is
A local MCP server for kintone, Cybozu's business application platform. It is unofficial — Cybozu publishes its own, and this README points at it — and its scope is unusually complete: alongside reading and writing records it can create apps, add and reconfigure fields, change form layouts, edit views, graphs, notifications, process management and access control, and deploy those changes to production.
What you get
- Records read, searched, created, updated and upserted on a duplicate-prevention field —
get_record,search_records,create_record,update_record,upsert_record - Process management driven properly: status transitions, assignee changes and comments —
update_record_status,update_record_assignees,add_record_comment,get_record_comments - Files uploaded and downloaded, with a documented caveat that files of 1MB or more may not download correctly in the current implementation —
upload_file,download_file - App configuration read in full: form layout and fields, actions, plugins, process management, views, graphs and all four notification kinds —
get_apps_info,get_form_layout,get_form_fields,get_app_actions,get_app_plugins,get_process_management,get_views,get_reports,get_notifications,get_per_record_notifications,get_reminder_notifications - Permissions inspected and evaluated at app, field and record level —
get_app_acl,get_field_acl,get_record_acl,evaluate_records_acl - Apps built and changed, then deployed to production with a status check —
create_app,add_fields,update_field,update_form_layout,update_app_settings,update_views,update_reports,update_notifications,update_process_management,deploy_app,get_deploy_status - Spaces, threads and guests managed —
get_space,update_space,update_space_body,get_space_members,update_space_members,add_thread,update_thread,add_thread_comment,add_guests,update_space_guests - Users and groups resolved —
get_users,get_groups,get_group_users - The current connection's domain and username, so the agent can report which tenant it is acting against —
get_kintone_domain,get_kintone_username
Requirements
A kintone account with the permissions you want the agent to have. Three values: KINTONE_DOMAIN as [subdomain].cybozu.com, KINTONE_USERNAME, and KINTONE_PASSWORD — a plain-text account password rather than an API token, which is the trust decision to make before installing. The easiest install is the .mcpb desktop extension from Releases, dragged into Claude Desktop's extensions panel, where you enter the connection details in a form and can disable individual tools you would rather not expose. Otherwise Node.js 20 or newer with pnpm or npm, and point the client at server.js.
Setup effort
Build from source — git clone https://github.com/r3-yamauchi/kintone-mcp-server
USE CASES
Finding and fixing records without opening kintone
Search the app for the records that match, read one in full, and update it — with upsert available when the record may not exist yet.
Moving work through a process
Change the record's status and assignee and leave a comment explaining why, rather than doing three clicks per record.
Understanding an app someone else built
Read its fields, form layout, views, process management and notification settings together to see how it is actually wired.
Adding a field and getting it live
Add the field, place it in the form layout, then deploy and check the deployment status rather than assuming it took.
Checking who can see what
Read the app, field and record-level permissions, and evaluate record access under a condition instead of reasoning about the rules.
Confirming which tenant you are connected to
Ask the server for its domain and username before running anything that writes — a one-call check against acting on the wrong environment.
59 tools
Listed in project docs. Your client may show a different list.
search_recordscreate_recordupdate_recordupsert_recordadd_record_commentupdate_record_statusupdate_record_assigneesget_record_commentsupload_filedownload_fileget_apps_infoget_form_layoutget_form_fieldsget_app_actionsget_app_pluginsget_process_managementget_app_aclget_field_aclget_record_aclevaluate_records_aclget_viewsget_reportsget_notificationsget_per_record_notificationsget_reminder_notificationscreate_appadd_fieldsupdate_fieldupdate_form_layoutupdate_app_settingsdeploy_appget_deploy_statusmove_app_to_spacemove_app_from_spaceupdate_app_aclupdate_field_aclupdate_viewsupdate_reportsupdate_notificationsupdate_per_record_notificationsupdate_reminder_notificationsupdate_process_managementupdate_app_actionsget_spaceupdate_spaceupdate_space_bodyget_space_membersupdate_space_membersadd_threadupdate_threadadd_thread_commentadd_guestsupdate_space_guestsget_usersget_groupsget_group_usersget_kintone_domainget_kintone_usernameBEFORE YOU INSTALL
What to know first
Tools you get
59 tools named in the project's documentation.
Requires
- node on PATH
- Node.js 20
- KINTONE_DOMAIN in your environment
- KINTONE_USERNAME in your environment
- KINTONE_PASSWORD in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
git clone https://github.com/r3-yamauchi/kintone-mcp-server
cd kintone-mcp-server
npm installMCP Clients
Claude Desktop
{
"mcpServers": {
"kintone": {
"command": "node",
"args": [
"<YOUR_PATH_TO_KINTONE_MCP_SERVER>/server.js"
],
"env": {
"KINTONE_DOMAIN": "<YOUR_SUBDOMAIN>.cybozu.com",
"KINTONE_USERNAME": "<YOUR_KINTONE_USERNAME>",
"KINTONE_PASSWORD": "<YOUR_KINTONE_PASSWORD>"
}
}
}
}