kintone MCP Server (Python3)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Optional log level for debugging (e.g., DEBUG, INFO, WARNING, ERROR). | |
| KINTONE_DOMAIN | Yes | The kintone domain URL (e.g., your-subdomain.cybozu.com). | |
| KINTONE_PASSWORD | No | Password for password-based authentication. | |
| KINTONE_USERNAME | No | Username for password-based authentication. | |
| KINTONE_API_TOKEN | No | API token for token-based authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recordsC | Get records from a kintone app |
| get_all_recordsA | Get all records from a kintone app (handles pagination automatically) |
| get_appsC | Get kintone apps information by name or other filters |
| get_recordC | Get a single record from a kintone app |
| add_recordC | Add a single record to a kintone app |
| add_recordsC | Add multiple records to a kintone app (max 100 records) |
| update_recordC | Update a single record in a kintone app |
| update_recordsC | Update multiple records in a kintone app (max 100 records) |
| get_commentsC | Get comments for a record |
| add_commentC | Add a comment to a record |
| update_statusC | Update the status of a record |
| update_statusesC | Update the status of multiple records (max 100) |
| upload_fileC | Upload a file to kintone |
| download_fileC | Download a file from kintone |
| get_appC | Get app information |
| get_form_fieldsB | Get form fields configuration |
| get_query_language_docB | Get comprehensive documentation about kintone query language syntax |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools have distinct purposes targeting specific resources and actions, such as add_record vs. update_record or get_record vs. get_records. However, get_all_records and get_records could cause confusion as both retrieve records, though the former handles pagination automatically, which is a subtle but potentially ambiguous distinction for agents.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs like add, get, update, download, and upload. The naming is uniform across all 17 tools, using snake_case throughout without any deviations or mixed conventions.
With 17 tools, the count is slightly high but reasonable for a kintone server covering CRUD operations, file handling, comments, and app management. It feels comprehensive without being overly bloated, though it borders on the upper limit of a well-scoped set.
The tool set provides complete coverage for the kintone domain, including full CRUD for records (add, get, update), batch operations, file upload/download, comment management, app and form field retrieval, and status updates. There are no obvious gaps, and agents can handle typical workflows without dead ends.