Kintone MCP. Manage custom business records directly from your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Kintone MCP Server connects your AI agent directly to your custom Kintone apps. You can manage data records, query metadata, and automate workflows without manual API calls.
It lets your agent list apps, read specific record details, update data, and even discover the field layouts of your entire organization's apps.
This cuts out the need for manual data exports and spreadsheet wrangling.
What your AI agents can do
Add record
Adds a new record to a Kintone app; requires a JSON object detailing the field codes and values.
Delete records
Deletes one or more records from a Kintone app; requires an array of record IDs.
Get app details
Retrieves general configuration details for a specific Kintone app.
Adds a new record to a specified Kintone app using a JSON object mapping fields to values.
Updates the fields and values of an existing Kintone record identified by its ID.
Retrieves all data for a single Kintone record from a specified app.
Lists multiple Kintone records from an app, allowing you to filter results using a custom query string.
Lists all Kintone apps and retrieves detailed configuration and field mapping information for each.
Retrieves a list of all available form fields for a specific Kintone app, helping understand the data structure.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Kintone MCP Server: 10 Tools for App & Record Management
This suite gives your agent full control over Kintone's data layer. You can list apps, read single records, query filtered lists, and write new data to your custom apps.
019d75c0add record
Adds a new record to a Kintone app; requires a JSON object detailing the field codes and values.
019d75c0delete records
Deletes one or more records from a Kintone app; requires an array of record IDs.
019d75c0get app details
Retrieves general configuration details for a specific Kintone app.
019d75c0get app layout
Shows the field layout and structure for a specific Kintone app.
019d75c0get record
Gets all the data for one specific record in an app.
019d75c0list apps
Lists every Kintone app ID, helping you target the right app for record operations.
019d75c0list form fields
Retrieves all form fields for a given app, showing the data structure you can work with.
019d75c0list records
Lists multiple records in an app, letting you filter the results with a query string.
019d75c0list space members
Lists all users and members within a specific Kintone collaboration space.
019d75c0update record
Modifies an existing Kintone record's data using its ID and new field values.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Kintone, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Kintone MCP Server connects your AI agent directly to your custom Kintone apps. You'll manage data records, query metadata, and automate workflows without manually calling APIs. It lets your agent list every app, read specific record details, update data, and discover the field layouts across your entire organization. You cut out the need for manual data exports and spreadsheet wrangling.
Create New Records
Your agent uses add_record to drop a new record into any Kintone app, needing just a JSON object that maps field codes to values. You can also update_record to modify an existing record's fields and values using its ID. You'll need delete_records to wipe out one or more records, supplying an array of record IDs.
Read and Find Records
Your agent gets all the data for one specific record with get_record. You can also list multiple records with list_records, letting your agent filter the results using a custom query string. If you just want to know what apps you've got, list_apps lists every Kintone app ID.
You can also list_form_fields to get all form fields for a given app, which shows you the data structure you can work with.
App Structure and Metadata
Your agent checks out the big picture with get_app_details, which grabs general configuration details for a specific Kintone app. You'll use list_form_fields to get a full list of all available form fields for an app, helping you understand the data structure. To understand the full layout, your agent uses get_app_layout to show the field layout and structure for a specific app.
You can also list_space_members to list all users and members within a specific Kintone collaboration space.
Managing Records and Data
Your agent can list_apps to see all the apps you've got. It can then get_app_details to check the general setup. You'll use list_form_fields to map out the data structure for a specific app before you write anything. Once you're ready, you can add_record to create new records, update_record to change old ones, or delete_records to take records out.
For reading data, get_record pulls all data from one record, and list_records lets you pull groups of records, letting you narrow down results with a query string. You can also list_space_members to see who's in a space.
How Kintone MCP Works
- 1 Subscribe to the Kintone server and provide your Kintone Subdomain and API Token.
- 2 Your AI client calls a tool, like
list_apps, and passes the necessary identifiers. - 3 The server uses your credentials to interact with the Kintone API, and your agent receives the structured data response.
The bottom line is, your agent talks directly to Kintone's backend, bypassing the UI entirely.
Who Is Kintone MCP For?
This is for Operations Engineers and Project Managers who spend too much time jumping between dashboards or writing repetitive API scripts. If your job involves moving data between systems or needing to audit records across multiple custom apps, this server saves hours.
Uses list_records and update_record to bulk-check project statuses or change ownership fields across many records.
Uses get_record and list_records to pull specific task details or query project status reports directly from the app data.
Uses list_apps and list_form_fields to map out data structures and understand how different custom apps are set up without manual inspection.
What Changes When You Connect
- Need to know what data is available? Use
list_appsto see every app ID. Then uselist_form_fieldsto understand exactly what fields that app uses before you try to write or update anything. - Tired of manual data entry? Your agent can use
add_recordorupdate_recordto populate records instantly. Just give it the data and the app ID. - Don't just read data, filter it. Running
list_recordswith a complex query string lets you pull only the 'Pending' status opportunities across hundreds of records. - Need to audit a single item? Use
get_recordto pull all details for one record. It's faster than opening the app and navigating to the record manually. - Need to know who can see the data?
list_space_membersshows all members of a space. This is crucial for understanding permissions and collaboration limits. - Change the data structure? Use
get_app_layoutto check the exact field settings for an app. This prevents your agent from sending data that doesn't match the required format.
Real-World Use Cases
Project Status Check
The PM needs to know the status of 15 projects but doesn't want to click through 15 dashboards. They ask their agent to 'Show all project records in the 'Project Tracker' app where status is Pending.' The agent runs list_records and returns the list, letting the PM triage the issues instantly.
New Employee Onboarding
The Ops Analyst gets a new hire's data sheet. Instead of logging into Kintone and filling out five different forms, they ask their agent to 'Add the new employee record to the 'Employee Directory' app.' The agent runs add_record and handles the entire data entry process.
Data Cleanup
A Business Analyst notices old, incomplete records. They ask the agent to 'Find all records in the 'Opportunity' app that haven't been updated in 90 days.' The agent uses list_records with a complex filter and then runs delete_records to clean up the stale data.
Role Mapping
The PM needs to confirm who has access to the main project space. They ask the agent to 'List all members of the main project space.' The agent runs list_space_members, providing an immediate list of authorized users.
The Tradeoffs
Guessing the App ID
The user tries to call get_record(app_id=12) without knowing the ID. The request fails, and the user wastes time guessing the correct numeric ID.
→
Always run list_apps first. This gives you a list of all available app IDs, ensuring you target the right place before running any record tools.
Ignoring Field Structure
The user tries to run add_record by guessing the field names, like passing 'Employee Name' instead of the required code 'name'. The record save fails because the structure is wrong.
→
Before adding or updating, use list_form_fields to get the exact field codes and names. This guarantees your data payload matches the app's schema.
Updating the Wrong Record
The user runs update_record(record_id=999) because they think it's the target record, but it's actually a test record. The wrong data gets overwritten.
→
Always use get_record or list_records first to confirm the record ID you intend to modify. Double-check the returned ID before running update_record.
When It Fits, When It Doesn't
Use this server if your process is data-centric: If you need to read, write, or query data stored in custom Kintone apps, this is your tool. You'll use list_apps to find the target, list_form_fields to check the schema, and then get_record, list_records, add_record, or update_record to perform the action.
Don't use this if your problem is pure process management (e.g., 'Who needs to approve this?'). For that, you might need a dedicated workflow tool. Don't use this if you need to manage assets outside of Kintone's structured apps. Stick to the data layer.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kintone. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually building reports from custom apps is a huge time sink.
Right now, if you need a report showing all 'Pending' opportunities across five different apps, you manually export five separate CSV files. You copy the columns into a master spreadsheet, clean up the headers, and then spend an hour cross-referencing data points. It's a mess.
With this server, you just ask your agent to 'Show all pending opportunities.' The agent runs `list_records` against the specific app, returns the clean data payload, and you get the final, filtered result in seconds. No CSVs needed.
Kintone MCP Server: Manage custom app records and metadata.
You don't have to log into Kintone and click through three different screens just to see what fields an app uses. You can use `get_app_layout` to instantly pull the entire field structure and data mapping into your IDE's console.
This changes everything. You get the data structure immediately. You don't have to guess the field codes or spend time navigating the UI—you just know the schema.
Common Questions About Kintone MCP
How do I list all my Kintone apps using `list_apps`? +
You simply ask your agent to run the list_apps tool. The agent returns a list of all your Kintone apps, including their unique IDs. You'll need these IDs for any record operation.
Can I update a record using `update_record` without knowing the ID? +
No, you must know the specific record ID. You can use get_record or list_records first to pull the record details and confirm the ID before running update_record.
What is the difference between `get_record` and `list_records`? +
get_record pulls all data for a single, specific record. list_records pulls a filtered list of multiple records from an app.
How do I find out what fields are available for a new app? +
Use the list_form_fields tool. It shows the field names and types for a given app ID, so you know exactly what data you can put into it.
Do I need to call `list_apps` every time I use `add_record`? +
No. You only need to run list_apps when you don't know the target app's ID. If you already know the app ID, you can skip that step.
How do I use `list_space_members` to check who is in a Kintone space? +
It lists all members and participants in a specific Kintone space. The output shows names, email addresses, and roles, which helps you manage team access.
When should I use `list_form_fields` instead of `get_app_layout`? +
list_form_fields gives a programmatic list of fields for an app. Use it when your agent needs to iterate over every field name and type, rather than just seeing the visual layout.
What data does `get_app_details` return, and why is it useful? +
It returns core information about a specific Kintone app, including its ID, name, and status. You need this basic metadata to confirm an app exists before attempting any record operations.
How do I find the App ID for a specific application? +
Use the list_apps tool to see a comprehensive list of all applications in your environment along with their unique App IDs.
Can I filter records using custom criteria? +
Yes, the list_records tool accepts an optional Kintone query string, allowing you to filter data based on field values, status, and more.
Is it possible to update an existing record via the agent? +
Absolutely. Use the update_record tool with the App ID and Record ID, providing a JSON object with the fields you wish to modify.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Design Pickle
Equip your AI agent to manage graphic design requests, track brand profiles, and monitor your production queue via the Design Pickle API.
Appointlet
Bring Appointlet scheduling directly into your AI agent — list schedules, track bookings, cancel events, and manage attendees seamlessly.
OpnForm
Create beautiful open-source forms with conditional logic, file uploads, and integrations that rival premium form builders.
You might also like
Recurly
Equip your AI to directly manage subscriptions, billing accounts, and invoices within your Recurly ecosystem without shifting interfaces.
Kitetags
Generate optimized hashtags for Instagram and TikTok posts with AI that analyzes trending tags and maximizes reach.
LearnUpon
Manage users, courses, and enrollments via the LearnUpon LMS API.