mcp-kintone-lite
Related Servers
Alternatives to mcp-kintone-lite
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceA Model Context Protocol server that enables Claude and other AI assistants to access and update Kintone data through natural language commands, supporting operations like record management, file handling, app administration, and space collaboration.7910AGPL 3.0

kintone MCP Serverofficial
AlicenseAqualityAmaintenanceOfficial MCP server for kintone, enabling AI assistants to manage kintone apps, records, and settings through natural language.20708 npm56Apache 2.0- AlicenseNot gradedqualityDmaintenanceMCP server for integrating with Bika.ai platform, enabling AI assistants to perform CRUD operations on databases, manage attachments, and utilize automation and webhooks.1MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with kintone data by providing comprehensive tools for record CRUD operations, file management, and workflow status updates. It supports secure authentication and automatic pagination to handle large datasets efficiently through the Model Context Protocol.17MIT
- AlicenseBqualityCmaintenanceMCP server for Microsoft Dynamics 365 Business Central, enabling AI assistants to perform CRUD operations, query data, and retrieve schemas via Business Central API v2.0.622 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server enabling AI assistants to perform CRUD operations on a Supabase database via a standardized interface.194MIT
TDQS
Scored across 10 tools
Each tool targets a distinct Kintone resource or operation—app listing, app details, records, form fields, layout, views, and CRUD for records. There is no overlap; descriptions clarify the purpose of each tool.
All tools follow the consistent pattern 'kintone_verb_noun' (e.g., kintone_create_record, kintone_get_record, kintone_list_apps). No mixing of cases or inconsistent verb forms.
With 10 tools, the set is well-scoped for a Kintone integration: covers app discovery, record CRUD, and metadata retrieval (fields, layout, views). This is appropriate for a 'lite' server.
The server covers the core workflow: listing apps, getting app details, record CRUD, and essential metadata (fields, layout, views). Minor gaps like bulk operations or file handling are acceptable for a lite version.