Kintone MCP. Control your low-code business data conversationally
Kintone MCP connects your AI agent directly to your Kintone business applications. It lets you manage complex operational data—including creating, reading, updating, and deleting records across multiple apps—all through natural conversation. You can list every app available or query specific fields without ever opening the UI. This gives developers and operations teams granular control over low-code workflows, treating your entire Kintone instance like a database you talk to.
Give Claude and any AI agent real-world access
The agent can list all Kintone apps and pull details on specific fields within them.
You can retrieve detailed information about the underlying spaces that host your applications.
The agent searches for records across any app, supporting advanced filtering using Kintone query syntax.
You can pull the complete data profile of a single record when you know its ID.
The agent generates and adds one or more new records into any app.
You can update multiple fields across several existing records simultaneously.
The agent deletes specified records from an app when they are obsolete.
Ask an AI about this
Waiting for input…
What AI agents can do with Kintone: 8 Tools for Deep Data Management
These tools give your AI agent the full capability to interact with Kintone. You can list apps, manage records, check field settings, and more.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Kintone MCPAdd Records
This tool adds one or more new records into a specified Kintone app.
Delete Records
This tool permanently removes selected records from an app.
Get App Fields
It retrieves the full settings and definitions for all fields in a given Kintone app.
Get Record
You can fetch comprehensive details for one specific record using its ID.
Get Space Details
This tool gets background information about the Kintone space where apps are hosted.
List Apps
It lists every single Kintone app that you have access to manage.
List Records
You can pull a list of records from an app, optionally filtering them with a query string.
Update Records
This tool changes the content of one or more existing records in an app.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 each 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 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The headache of jumping between departmental dashboards
Today, checking a single client's status means opening the 'Sales Pipeline' app to see their deal value. Then, you have to jump over to the 'Customer DB' app just to verify if they are still marked as an active prospect. If that info is wrong, you copy the ID and paste it into the 'HR Requests' dashboard so someone can fix it. It’s a painful cycle of clicking, copying, and waiting.
With this MCP, your AI agent handles the whole chain. You just ask one question: 'What is the current status of Acme Corp across all apps?' The agent uses multiple tools—like list_records and get_record—to pull that data instantly and give you a single, consolidated answer.
Control records with add_records
Manual record entry is slow. If your team gets 15 new leads every morning, someone has to manually open the 'Customer DB' app and fill out 15 separate forms—Name, Email, Industry, Status, etc. That’s tedious data duplication.
Now, you feed the list of 15 leads into your agent using add_records. The MCP takes that bulk data and programmatically creates all 15 records in the correct format. It's instant population.
What Kintone MCP does for your AI
You manage complex business data stored in Kintone using only natural conversation. Instead of logging into separate applications or building custom API calls, you just ask your AI agent what you need done. This MCP lets you inspect the structure of any app—checking field types and configurations—and then perform full CRUD (Create, Read, Update, Delete) operations on records across multiple apps.
Need to query a specific deal in the 'Sales Pipeline' while simultaneously checking the details of the 'Customer DB'? You can do that. Your AI client handles the data flow, making your Kintone instance feel like one unified, conversational database. Vinkius hosts this MCP, giving your agent access to every toolset you need for deep operational control.
019dd111-3832-7224-80e0-4fa131f76190 How to set up Kintone MCP
The bottom line is, your AI client treats your entire low-code platform like an extension of its memory, allowing you to work with structured business data conversationally.
Subscribe to this MCP and provide your Kintone domain and API Token.
Your AI client connects, authenticating access to all the apps and spaces you manage within Kintone.
You speak a request—like 'Show me all deals over $50K in Sales Pipeline'—and the agent uses the appropriate tools to execute the data action.
Who uses Kintone MCP
This MCP is built for the developer or operations specialist tired of switching between multiple tabs and manually running reports. If your job involves coordinating data across different departmental apps (like sales, inventory, and HR), this gives you back hours of clicking.
You use the MCP to check app field settings or list records in multiple apps to prepare a cross-departmental report without opening any dashboards.
You connect your AI workflows directly to Kintone data, using tools like add_records and update_records to automate the creation or modification of records based on external triggers.
You use it to query metrics across different apps—for example, pulling all active prospects from both the 'Sales Pipeline' and 'Customer DB' apps at once.
Benefits of connecting Kintone MCP
You gain total visibility into your platform structure. Use list_apps and get_app_fields to map out every available app and field type without clicking through the UI.
Eliminate manual reporting cycles. Instead of querying reports, simply ask the agent to list records or run a query on data that spans multiple apps simultaneously.
Automate daily maintenance tasks instantly. Need to onboard new client data? Use add_records to populate dozens of records across different departmental apps in one prompt.
Maintain clean data integrity. When business logic changes, use update_records and delete_records directly through your agent instead of having to manually edit the source app.
Simplify troubleshooting. If a record is missing or incorrect, you don't have to guess; use get_record with just an ID to pull the full profile instantly.
Kintone MCP use cases
Auditing old data for compliance
A manager needs to know who was assigned to a specific project three months ago. They tell their agent, 'List records in the Project Tracker app where Status is Closed and find the owner.' The agent uses list_records and get_record to pull the required historical assignment details.
Migrating client data
A developer needs to move 50 new user entries into the HR system. They use add_records, providing a JSON array of records, which populates the target app instantly without any manual form entry.
Correcting old client information
The sales team found that 10 deals have incorrect owner names. They prompt the agent to use update_records across the 'Sales Pipeline' app, correcting all owners and ensuring data consistency.
Building a cross-app dashboard view
An analyst needs to know if an inventory item (Inventory App) is ready for a client who was recently onboarded (Customer DB App). They query both apps sequentially using list_records and get_record, creating a unified data report.
Kintone MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to run simple reports
A user tries to generate a report that requires joining fields from the 'Inventory' app with data from the 'HR Requests' app, leading them to open two separate dashboards and copy-paste results.
Use your AI client and list_records. By providing both app names and combining their field filters in a single query, you let the agent pull the combined data set into one conversational response.
Manually checking every record
A manager has to click through hundreds of records in a large 'Customer DB' app just to verify if a specific field (like Annual Revenue) was filled out correctly.
Use list_records. You can provide the optional query string filter, asking for all records where the Annual Revenue field is empty or below a certain threshold.
Misunderstanding app structure
A new developer assumes an app has a 'Client Email' field when it's actually called 'Contact Email', causing their integration to fail.
Before writing code, use get_app_fields. This tool inspects the full configuration and names of all fields, preventing structural errors in your agent’s logic.
When to use Kintone MCP
Use this MCP if you need programmatic access to the raw data inside Kintone apps. Specifically, if your workflow needs to read a record's content (get_record), change it (update_records), or create new records without human intervention, this is your tool. Don't use it if you simply want to view the UI; for that, just open Kintone. Also, don't rely on this MCP to build complex user interfaces—it handles data flow and manipulation only. If your goal is merely to list available apps or check field definitions before writing any code, then get_app_fields and list_apps are exactly what you need.
Frequently asked questions about Kintone MCP
Can I use Kintone MCP to see what apps are available? +
Yes, you can use list_apps. This tool retrieves a comprehensive list of all the specific Kintone applications that your agent has access to.
How do I check the fields in an app using Kintone MCP? +
Use get_app_fields. It pulls up the full configuration, telling you every field name and its data type (like dropdown or text) so your agent knows exactly how to interact with it.
What is the difference between list_records and get_record in Kintone MCP? +
list_records pulls a filtered list of multiple records, while get_record retrieves all available data for one specific record using its unique ID.
Can I bulk update multiple client records with Kintone MCP? +
Yep. Use update_records. You can pass a batch of JSON objects to change fields, like updating the 'Status' field for 20 different clients at once.
Does Kintone MCP allow me to delete old records? +
Yes, you can use delete_records. This tool is designed to remove specified records from an app when they are no longer needed or compliant.