Bring Product Management
to Cursor
Learn how to connect Craft.io to Cursor and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Craft.io MCP Server?
Connect your Craft.io product management account to any AI agent and simplify how you coordinate your product strategy, manage features, and monitor roadmaps through natural conversation.
What you can do
- Workspace Oversight — List all product management workspaces and retrieve detailed metadata and configurations.
- Feature & Epic Tracking — List, query, and create new items (features, stories, epics) within your workspaces to manage your backlog.
- Portfolio Control — List and query product portfolios to understand high-level organizational distribution and strategy.
- Data Insights — Fetch complete metadata, descriptions, and current status for any specific product item via AI.
- Roadmap Monitoring — Track the progress of features and epics directly from your agent to stay on top of your release cycle.
- Operational Visibility — Check account status and verify project metadata directly from Claude, Cursor, or any MCP client.
How it works
1. Subscribe to this server
2. Enter your Craft.io API Key and Account ID (found in your account settings)
3. Start managing your product ecosystem from your favorite AI assistant
Who is this for?
- Product Managers & Owners — quickly retrieve feature details and update backlog items via simple AI commands.
- Engineering Leads — monitor epic progress and verify feature requirements directly from the workspace.
- Product Operations — manage workspace distributions and verify portfolio metadata via the AI assistant.
Built-in capabilities (13)
Verify connectivity
Create an item
Get company details
Get competitors
Get company employees
Get company financials
Get company news
Get item details
Get portfolio details
List workspace items
List portfolios
List workspaces
Search companies
Why Cursor?
Cursor's Agent mode turns Craft.io into an in-editor superpower. Ask Cursor to generate code using live data from Craft.io and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Craft.io in Cursor
Craft.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Craft.io to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Craft.io in Cursor
The Craft.io MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Craft.io for Cursor
Every tool call from Cursor to the Craft.io MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all the items in a specific workspace via AI?
Yes! Use the list_workspace_items tool and provide the Workspace ID. Your agent will retrieve all features, stories, and epics organized within that environment.
How do I add a new feature to my backlog using the agent?
Use the create_product_item action. Provide the Workspace ID and the title of the feature. The agent will instantly create the record in your Craft.io account.
Is it possible to list all my product portfolios via AI?
Absolutely. Use the list_product_portfolios query. The agent will retrieve the complete list of portfolios configured in your account, allowing you to monitor high-level strategy.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
