mcp -kintone

This MCP server provides a bridge to interact with kintone data through AI tooling. By running the kintone MCP server and configuring an MCP client (for example Claude Desktop), you can query, update, and explore kintone records and apps using natural language prompts. The server leverages the configured environment variables to authenticate with your kintone instance and enforce access controls for specified apps. Once connected, you can ask questions like what is the latest status of a project, update a record’s progress, or filter and retrieve lists of records across apps. The UX is designed for conversational AI, enabling you to leverage AI assistants to compose queries, perform updates, and navigate kintone data without manual API calls.

Prerequisites:

• A supported operating system (Windows, macOS, or Linux) with the ability to run a native binary for the MCP server.
• Access to the latest release of the MCP server for kintone from the project releases page.

Installation steps:

1. Download the latest release of the MCP server for kintone from the releases page and save the executable to a desired location.
2. Ensure the executable has execute permissions (on Linux/macOS) or is runnable on Windows.
3. Prepare your kintone credentials and tokens as described in the README (base URL, username/password or API token).
4. Create or edit your MCP client configuration to point to the server executable and supply required environment variables (see example in the README).
5. Start the MCP server by running the executable (no additional runtime required).
6. In your MCP client (e.g., Claude Desktop), add a new mcpServers entry using the path to the executable and the required environment variables, then connect.

Notes:

• If you switch from a local setup to the official MCP server, you may need to adjust environment variables or access controls accordingly.

Environment variables:

• KINTONE_BASE_URL is required. Provide the base URL for your kintone instance.
• KINTONE_USERNAME and KINTONE_PASSWORD or KINTONE_API_TOKEN must be provided (one of these authentication methods).
• KINTONE_ALLOW_APPS and KINTONE_DENY_APPS control access to specific kintone apps; deny rules take precedence over allow.
• Restart the client (e.g., Claude Desktop) after changing environment variables to apply changes.

Common issues:

• Incorrect base URL or credentials will prevent authentication; double-check domain and user permissions.
• If the MCP server cannot reach kintone APIs due to network restrictions, ensure outbound access is allowed.
• If using Windows, ensure the executable path in the MCP client config matches the actual file location.

This project notes that an official kintone MCP server is available; consider migrating to the official server when feasible for ongoing maintenance and feature parity.