Authentication is Basic — a Kintone username and password sit in the client config, which means the server can do whatever that account can do, in every app that account can see, including deletes. If that is a full-access account, scope it down before wiring this in: a dedicated Kintone user with permissions on only the apps you want reachable is the difference between a query tool and a standing risk. What you get in exchange is direct: the apps, their field definitions, and records you can filter and change from a conversation.
A lightweight Python MCP server for Kintone, Cybozu's business-application platform. It authenticates with Basic Authentication against your subdomain, lists the apps your account can see, reads their form fields, queries records with filtering and pagination, and performs create, read, update and delete on them.
- The Kintone apps your account has permission to see, listed
- The form fields of a given app, so records can be addressed by their real field names
- Record queries with filtering and pagination
- Create, read, update and delete operations on records
- Input validation on the way through, and credentials read from the environment rather than hard-coded
Python 3.10 or higher and a Kintone account. Three environment variables: `KINTONE_SUBDOMAIN` (the part before the cybozu.com domain), `KINTONE_USERNAME` and `KINTONE_PASSWORD`. `pip install mcp-kintone-lite`, or let the client run it directly with `uvx --from mcp-kintone-lite mcp-kintone-lite`, which is what the documented Claude Desktop entry does. The package is `mcp-kintone-lite` 0.1.0 in pyproject; a checkout plus `uv sync` or Poetry is the development path.
One command plus a key — uvx --from mcp-kintone-lite mcp-kintone-lite, then supply credentials