What features does Kintone MCP server provide?

Q: What features does Kintone MCP server provide?

Deployment options: Supports MCPB packaging for Claude Desktop, a Docker container image, and a global npm package to run a local MCP server.. Flexible authentication methods: Configures access with base URL, username/password, API tokens (comma-separated, up to 9), Basic authentication, and client certificates; password takes precedence over API token; CLI arguments override environment variables.. Config file support and examples: Defines MCP servers in JSON configuration files. Examples show Claude Code (.mcp.json) and Cursor (.cursor/mcp.json) configurations.. CLI and environment configuration: Supports CLI arguments (--base-url, --username, --password, --api-token, etc.) and corresponding environment variables; options can be combined with precedence rules.. Proxy support: Provides HTTPS proxy configuration via HTTPS_PROXY (with optional credentials) for network access.. Kintone operation tools: Includes a suite of tools for common Kintone tasks, such as getting apps, forms, records, updating layouts, and deploying apps.. Documentation and authentication guide: Links to authentication guide and docs for configuring authentication settings.. Privacy and licensing: Connects to the Kintone REST API and is licensed under Apache 2.0.

Kintone MCP Server 2025: Features & Setup Guide

Overview

kintone MCP Server is the official local MCP server for Kintone. It can be deployed as MCPB for Claude Desktop, as a Docker container image (ghcr.io/kintone/mcp-server), or as a global npm package (@kintone/mcp-server). It enables running a local MCP server to bridge AI tooling and the Kintone REST API. The server supports flexible authentication and connection options via CLI arguments (--base-url, --username, --password, --api-token, etc.) and corresponding environment variables (KINTONE_BASE_URL, KINTONE_USERNAME, KINTONE_PASSWORD, KINTONE_API_TOKEN). It also supports Basic authentication, client certificates (PFX), and proxy configuration (HTTPS_PROXY). Configuration files are supported for defining MCP servers, with examples for Claude Code (.mcp.json) and Cursor (.cursor/mcp.json). An example configuration demonstrates how to start a server with environment-variable mappings. The MCP server exposes a suite of Kintone tools (e.g., kintone-get-apps, kintone-get-records, kintone-update-form-fields, kintone-deploy-app, etc.) to perform app, form, and record operations. The project references authentication documentation, privacy policy, and is licensed under Apache 2.0.

Features

Deployment options

Supports MCPB packaging for Claude Desktop, a Docker container image, and a global npm package to run a local MCP server.

Flexible authentication methods

Configures access with base URL, username/password, API tokens (comma-separated, up to 9), Basic authentication, and client certificates; password takes precedence over API token; CLI arguments override environment variables.

Config file support and examples

Defines MCP servers in JSON configuration files. Examples show Claude Code (.mcp.json) and Cursor (.cursor/mcp.json) configurations.

CLI and environment configuration

Supports CLI arguments (--base-url, --username, --password, --api-token, etc.) and corresponding environment variables; options can be combined with precedence rules.

Proxy support

Provides HTTPS proxy configuration via HTTPS_PROXY (with optional credentials) for network access.

Kintone operation tools

Includes a suite of tools for common Kintone tasks, such as getting apps, forms, records, updating layouts, and deploying apps.

Documentation and authentication guide

Links to authentication guide and docs for configuring authentication settings.

Privacy and licensing

Connects to the Kintone REST API and is licensed under Apache 2.0.