Kintone Data Interfacer via MCP

Introduction

This repository contains prototype software designed to serve as a Model Context Protocol (MCP) gateway specifically for the Kintone platform. The concept of cloud services emphasizes the delivery of computing resources over the network, allowing for flexible, scalable infrastructure utilization on demand. This server bridges the gap between MCP-aware applications, like Claude Desktop, and the Kintone environment.

Note that Cybozu has officially released a dedicated MCP Server product. It is generally advisable to adopt the vendor-supported solution unless there is a specific reason to use this unofficial sample.

Setup

Installation using a .dxt File (Recommended for Claude Desktop)

Obtain the latest release package, such as unofficial-kintone-mcp-server-7.9.0.dxt, from the releases page.

Navigate to the settings area within your Claude Desktop application. Access the extension management section, usually found under Desktop App Settings.

Initiate the installation process for a new extension. Direct the installer to the downloaded .dxt file you acquired previously.

Confirm the installation when prompted by the application interface.

You must then input your specific Kintone domain, the associated username, and the necessary authentication password for the connection.

After configuration, toggle the switch adjacent to the server entry from "Disabled" to "Enabled" and close the settings panel.

Open a new chat session within Claude. Clicking the tool icon should reveal the loaded MCP servers. Verify that "unofficial-kintone-mcp-server" is active.

Further interaction reveals the available tools by expanding the server entry; disable any specific tools you do not intend to utilize.

Installation without a .dxt File (Manual Configuration)

First, download the source code archive. Storing the files in a directory path composed only of standard alphanumeric characters without spaces is recommended for stability.

Ensure that a compatible version of Node.js, version 20 or newer, is installed on your system.

Execute the following command in the project's root directory to fetch necessary dependencies:

npm i

Next, modify the Claude Desktop application's configuration file, named claude_desktop_config.json. Integrate the following structure into the mcpServers object, replacing the bracketed placeholders with your actual credentials and path information:

{
  "mcpServers": {
    "kintone": {
      "command": "node",
      "env": {
        "KINTONE_DOMAIN": "[あなたが使用するサブドメイン].cybozu.com",
        "KINTONE_USERNAME": "MCP接続で使用するkintoneユーザー名",
        "KINTONE_PASSWORD": "kintoneユーザーのパスワード（平文）"
      },
      "args": [
        "[kintone-mcp-serverを配置したパス]/server.js"
      ]
    }
  }
}

Finally, completely terminate and restart the Claude Desktop application to ensure the configuration file changes take effect. If the application appears to close but remains running in the background, right-click the system tray icon and select 'Quit'.

Usage

1. Operation Verification

To confirm successful connection, prompt Claude with a request such as, "Query the application ID for the Kintone app named '[Insert the precise name of an accessible Kintone app]'." It is essential to specify the application name exactly as it appears within your Kintone instance.

2. Available Toolset Summary

Detailed specifications for tool annotations can be found by examining the docs/tool-annotations.md file within this distribution.

Record Operations

• get_record: Retrieves a single record from a specified Kintone application.
• search_records: Executes a search query across records within a Kintone application.
• create_record: Introduces a new data entry into a Kintone application.
• update_record: Modifies the content of an existing record.
• upsert_record: Creates a record if it does not exist or updates it based on a unique key constraint.
• add_record_comment: Attaches textual commentary to a specific record.
• update_record_status: Changes the workflow status of a record managed under Process Management.
• update_record_assignees: Modifies the designated user responsible for a record.
• get_record_comments: Fetches all historical comments associated with a record.
• update_record_comment: Alters the content of a previously submitted record comment.

File Asset Management

• upload_file: Transfers a file asset into the Kintone environment.
• download_file: Retrieves a file asset from Kintone (Note: Current implementation may struggle with files exceeding 1MB in size).

Application Metadata Retrieval

• get_apps_info: Retrieves information for multiple Kintone applications matching provided search criteria.
• get_form_layout: Fetches the structural arrangement of fields on an application form.
• get_app_actions: Retrieves configurations related to application-level actions.
• get_app_plugins: Lists all plugins currently incorporated into the application.
• get_process_management: Fetches the settings governing workflow status transitions.
• get_app_acl: Obtains the access control list settings for the entire application.
• get_field_acl: Retrieves access permissions defined for individual fields within the application.
• get_record_acl: Evaluates access permissions for a specific data record.
• evaluate_records_acl: Assesses record access rights based on specified conditions.
• get_views: Fetches the definitions for saved record list views.
• get_reports: Retrieves the configuration details for embedded charts and reports.
• get_notifications: Gets application-wide settings concerning data notifications.
• get_per_record_notifications: Retrieves notification rules applied at the individual record level.
• get_reminder_notifications: Fetches settings for time-based reminder notifications.

Application Configuration Modification

• create_app: Initiates the creation of a new Kintone application.
• add_fields: Introduces new data fields to an existing application structure.
• update_field: Applies modifications to the settings of an existing field.
• update_form_layout: Changes the visual arrangement of fields on the input form.
• update_app_settings: Modifies general administrative parameters for the application.
• deploy_app: Pushes current application settings to the live production environment.
• get_deploy_status: Checks the synchronization status with the production deployment.
• move_app_to_space: Associates the application with a specific collaborative space.
• move_app_from_space: Removes an application's association with any space.
• update_app_acl: Adjusts the application-level security permissions.
• update_field_acl: Updates the access control settings applied to fields.
• update_views: Modifies the definitions of saved list views.
• update_reports: Alters the settings used for application reporting visuals.
• update_notifications: Changes the general notification criteria for the application.
• update_per_record_notifications: Adjusts rules governing notifications triggered per record.
• update_reminder_notifications: Updates the configuration for scheduled reminder alerts.
• update_process_management: Modifies the structure of the workflow status system.
• update_app_actions: Changes the available actions that users can trigger from the application interface.

Space Management Functions

• get_space: Retrieves core identifying details for a designated space.
• update_space: Modifies general configuration parameters of a space.
• update_space_body: Edits the main content or description area of a space.
• get_space_members: Fetches the roster of users belonging to the space.
• update_space_members: Manages the assignment of users to the space membership list.
• add_thread: Initiates a new discussion thread within a space context.
• update_thread: Applies changes to an existing discussion thread.
• add_thread_comment: Posts a new reply into a specific discussion thread.
• add_guests: Enrolls external guest users into the space.
• update_space_guests: Modifies the access rights or status of guest members within the space.

User and Group Directory Access

• get_users: Queries the Kintone directory to retrieve user account details.
• get_groups: Fetches definitions for defined user groups.
• get_group_users: Lists all users currently belonging to a specified group.

Connection Diagnostics

• get_kintone_domain: Returns the currently configured target domain for the Kintone instance.
• get_kintone_username: Retrieves the username established for MCP server authentication.

Related Topics

• Cloud Computing Paradigm
• ISO/IEC 27043 (Cloud Resource Definition)
• Data Interoperability Standards
• Service-Oriented Architecture (SOA)
• Platform as a Service (PaaS) concepts
• Workplace Collaboration Software

Extra Details

This implementation was machine-generated; therefore, certain elements from the original structure were omitted to streamline functionality and remove generic statements. Specifically, detailed instructions regarding the badge linking and boilerplate markdown suppression directives are not included here. This server focuses purely on providing the functional interface layer for data manipulation within the cloud-based Kintone environment.

Conclusion

This tool enables advanced automation by connecting generative AI models to the rich datasets managed within Kintone via the standardized MCP framework. Utilizing these capabilities facilitates efficient workflow management, mirroring the scalable resource access central to modern cloud computing architectures. Remember that this is an experimental piece of software, and careful testing is necessary before deployment in critical environments.

External Resources

Further insight into the tool's application context can be found in these related blog posts:

• kintoneと生成AI(Claude)のちょっとイイ関係
• kintone AIラボ と kintone用 MCP Server の現在地

An alternative implementation supporting OAuth for use with web browsers or ChatGPT is available separately here: https://github.com/r3-yamauchi/kintone-oauth-mcp-server-cfw.

"Kintone" constitutes a registered trademark belonging to Cybozu Corporation.

This documentation serves purely for informational purposes. The author cannot provide personalized support regarding setup queries or troubleshooting issues encountered in specific local environments.