How to Use the Kintone MCP in CrewAI

Deploy an autonomous CrewAI team to manage your Kintone apps. Assign agents to monitor, analyze, and update records 24/7.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Kintone MCP to CrewAI

Create your Vinkius account to connect Kintone to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Kintone with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Kintone Monitoring

Configure a 'Monitoring Agent' in your crew. Its only job is to run `list_records` on your support tickets app every five minutes with a query for `status = "new"`. When it finds a new ticket, it doesn't solve it. It passes the record ID to a 'Triage Agent' in the same crew. This separation of duties is what makes CrewAI powerful. One agent watches, another thinks.

Collaborative Data Processing

The 'Triage Agent' gets a record ID. It uses `get_record` to fetch the full ticket details. Based on the content, it decides which specialist agent should handle it—billing, technical, or sales. The 'Specialist Agent' takes over, performs its own actions, and then uses `update_record` to add its notes and change the status in Kintone. The original record has now been touched by a whole team, automatically.

Dynamic CrewAI Tasking via an MCP Server

You can have a 'Setup Agent' that runs once when the crew starts. It uses `list_apps` and `list_form_fields` to build a shared context of the available Kintone environment. This context is then available to all other agents in the crew. They don't need to hardcode app IDs. They can ask the crew's shared memory for the 'lead_tracking_app_id' and get the right value. This MCP Server makes your crew adaptable.

Setup guide

Set up Kintone MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Kintone tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Kintone Analyst",
    goal="Access and analyze Kintone data via MCP.",
    backstory="Expert analyst with direct Kintone access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Kintone transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Kintone Analyst",
        goal="Access and analyze Kintone data via MCP.",
        backstory="Expert analyst with direct Kintone access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Kintone transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Kintone now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Kintone MCP in CrewAI

Yes, that's the standard CrewAI pattern. A 'Researcher' agent can use `list_records` to find work, then pass the record IDs to a 'Writer' agent equipped with the `update_record` tool.

Assign a dedicated 'Auditor' agent whose first task is to run `list_apps`. It can then place the correct App ID into the crew's shared context for other agents to use.

Yes. An 'Analyst' agent could identify a list of records for deletion, and pass those IDs to a 'Janitor' agent that has permission to execute a single `delete_records` call.

It's simple. The entire crew shares a single Vinkius MCP endpoint token passed during setup. Vinkius manages the secure connection to Kintone on your behalf.

The team can only access the Kintone record data and app metadata that your agents explicitly request with tools like `get_record`. Each session is isolated, and data access is logged through Vinkius.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript