Kintone Oauth Cfw MCP Server

Most AI and media services work still happens through a UI a human drives. Kintone Oauth Cfw MCP server moves it into the conversation instead. 2025年9月11日現在 ChatGPT Web版 においては ChatGPT の Pro または Plus アカウントで 設定 → コネクタ→ 詳細設定 → 開発者モード を有効にすることにより ベータ版として利用できるという状況のようです。.

The tools it exposes

The server publishes 14 tools. What each one is for:

• getRecords — レコード一覧を取得
• getRecord — 単一レコードを取得
• addRecord — レコードを追加
• addRecords — 複数レコードを一括追加
• updateRecord — レコードを更新
• getRecordComments — レコードのコメントを取得
• addRecordComment — レコードにコメントを投稿
• evaluateRecordsAcl — レコードのアクセス権を評価
• getApp — アプリ基本情報を取得
• getAppFields — フィールド一覧を取得
• searchApps — アプリを検索
• getAppSettings — アプリの一般設定を取得

What it needs from you

Configuration is passed through the environment: CYBOZU_CLIENT_ID, CYBOZU_CLIENT_SECRET, CYBOZU_SUBDOMAIN, COOKIE_ENCRYPTION_KEY, WORKER_URL, GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Kintone Oauth Cfw's toolset — getRecords, getRecord, addRecord and 11 more — is a fair guide to whether it matches your workflow. It is maintained by r3-yamauchi; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Kintone Oauth Cfw.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.