How to Use the CrewAI Platform MCP in Cursor

Q: How do I configure the CrewAI Platform MCP Server in Cursor?

Create a .cursor/mcp.json file in your project root. Drop in the server command or remote URL and turn on Agent mode.

Q: How does Cursor pull CrewAI Platform task logs?

It calls getrunstatus behind the scenes. That pulls the explicit cloud logging traces straight into your editor context.

Q: Does Cursor store my CrewAI Platform cloud logging traces?

No. When you pull vault limits via getrunstatus, the data streams directly into your editor memory. The isolated MCP sandbox destroys those logs completely after the connection closes.

Trigger and debug CrewAI workflows while coding inside Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CrewAI Platform MCP to Cursor

Create your Vinkius account to connect CrewAI Platform to Cursor 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 CrewAI Platform with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run crews from your Cursor editor

The `kickoff_crew` tool provisions JSON payloads to start your multi-agent jobs directly from the IDE chat. Cursor never guesses how your agents respond. It actually fires off the job and generates hard customer bindings while you write code. Stopping a runaway process is critical when you test locally. Agent mode fires `cancel_run` to inspect deep internal arrays mitigating specific plan math. You never have to leave your code window to kill a bad background job.

Pull live CrewAI Platform MCP Server data

The `get_crew` tool performs structural extraction of the properties driving your account logic. Reading your active configuration happens directly via this integration. Instead of hardcoding mock agent IDs, your editor pulls the real IDs straight from the platform. Finding available environments takes one prompt. Calling `list_crews` identifies bounded CRM records inside your headless setup. Your editor knows exactly which autonomous groups exist before it writes the code to interact with them.

Debug agents and tasks inline

The `get_agent` tool enumerates the explicitly attached structured rules for any single agent. Calling `list_agents` vaporizes explicit validations to extract rich churn flags across your setup. If an agent fails to execute, you debug the billing exports right in your project files. Task tracking gives you the rest of the picture. When the editor runs `list_tasks` or `get_task`, it identifies the precise active arrays tied to your native gateway authentication. You see exactly where a job stalled without opening a browser tab.

Setup guide

Set up CrewAI Platform MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the CrewAI Platform MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent CrewAI Platform transactions." If the MCP tools are loaded correctly, Cursor will call the CrewAI Platform tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "crewai-platform-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 CrewAI. 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 CrewAI Platform 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 CrewAI Platform MCP in Cursor

Create a `.cursor/mcp.json` file in your project root. Drop in the server command or remote URL and turn on Agent mode.

Yes. The editor provisions the JSON payload and starts the crew right from the chat panel.

It calls `get_run_status` behind the scenes. That pulls the explicit cloud logging traces straight into your editor context.

You skip the terminal completely. Cursor handles all the tool calls and data formatting inline.

No. When you pull vault limits via `get_run_status`, the data streams directly into your editor memory. The isolated MCP sandbox destroys those logs completely after the connection closes.

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