Kintone Remote FAQs

Question 1

What is Kintone Remote's primary function?

Accepted Answer

Kintone Remote wraps the official kintone Model Context Protocol (MCP) server, enabling it to operate as a centralized, server-side instance for remote and multi-user access, enhancing collaborative API development.

Question 2

How does Kintone Remote facilitate multi-user access?

Accepted Answer

By running as a server-side instance, Kintone Remote allows multiple users to connect and utilize kintone MCP functionalities. Each user logs in securely with their individual kintone account.

Question 3

What security measures does Kintone Remote implement?

Accepted Answer

It uses OAuth 2.1 compliant authentication with JWE-encrypted tokens for secure user sessions. For deployment, utilizing HTTPS via a reverse proxy is strongly recommended to protect login information.

Question 4

Does Kintone Remote retain all features of the official kintone MCP server?

Accepted Answer

Yes, Kintone Remote is designed to fully retain all functionalities of the official kintone MCP server, providing a consistent experience for developers.

Question 5

Are there any known limitations to Kintone Remote?

Accepted Answer

Currently, it primarily supports ID+Password authentication via OAuth 2.1 (it does not support 2FA, API tokens, or Basic authentication). Attachment downloads are also not supported.

Kintone Remote

Kintone Remote

주요 기능

사용 사례

주요 기능

사용 사례