kintone official MCP server
kintone official MCP server. The kintone mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
[![ci][ci-badge]][ci-url] [![npm version][npm-badge]][npm-url] [![License: Apache 2.0][license-badge]][license-url] [![Install MCP Server][cursor-badge]][cursor-url]
Everything the assistant can do here goes through one of these:
Cursor — .cursor/mcp.json [ref]kintone-get-apps — 複数のアプリ情報を取得kintone-get-app — 単一アプリの詳細情報を取得kintone-get-form-fields — アプリのフィールド設定を取得kintone-get-form-layout — アプリのフォームレイアウトを取得kintone-update-form-fields — アプリのフィールド設定を更新kintone-update-form-layout — アプリのフォームレイアウトを更新kintone-delete-form-fields — アプリのフィールドを削除kintone-get-process-management — プロセス管理設定を取得kintone-get-app-deploy-status — アプリ設定の運用環境への反映状況確認kintone-get-general-settings — アプリの一般設定を取得kintone-add-form-fields — アプリにフィールドを追加You will need 6 environment variables: KINTONE_BASE_URL, KINTONE_USERNAME, KINTONE_PASSWORD, HTTPS_PROXY, KINTONE_API_TOKEN, KINTONE_PFX_FILE_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @kintone/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Kintone's toolset — Cursor, kintone-get-apps, kintone-get-app and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kintone; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | .cursor/mcp.json \[[ref](https://docs.cursor.com/ja/context/mcp)] |
| kintone-get-apps | 複数のアプリ情報を取得 |
| kintone-get-app | 単一アプリの詳細情報を取得 |
| kintone-get-form-fields | アプリのフィールド設定を取得 |
| kintone-get-form-layout | アプリのフォームレイアウトを取得 |
| kintone-update-form-fields | アプリのフィールド設定を更新 |
| kintone-update-form-layout | アプリのフォームレイアウトを更新 |
| kintone-delete-form-fields | アプリのフィールドを削除 |
| kintone-get-process-management | プロセス管理設定を取得 |
| kintone-get-app-deploy-status | アプリ設定の運用環境への反映状況確認 |
| kintone-get-general-settings | アプリの一般設定を取得 |
| kintone-add-form-fields | アプリにフィールドを追加 |
| kintone-get-records | 複数のレコードを取得 |
| kintone-add-records | 複数のレコードを追加 |
{
"mcpServers": {
"kintone": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KINTONE_BASE_URL",
"-e",
"KINTONE_USERNAME",
"-e",
"KINTONE_PASSWORD",
"ghcr.io/kintone/mcp-server:latest"
],
"cwd": "${cwd}",
"env": {
"KINTONE_BASE_URL": "https://example.cybozu.com",
"KINTONE_USERNAME": "username",
"KINTONE_PASSWORD": "password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| KINTONE_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| KINTONE_USERNAME | Configuration value read at startup. | Optional |
| KINTONE_PASSWORD | Configuration value read at startup. | Optional |
| HTTPS_PROXY | Configuration value read at startup. | Optional |
| KINTONE_API_TOKEN | Credential the server authenticates with. | Yes |
| KINTONE_PFX_FILE_PATH | Filesystem location the server is allowed to use. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.