Bring Product Management
to CrewAI
Learn how to connect Craft.io to CrewAI 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 CrewAI?
When paired with CrewAI, Craft.io becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Craft.io tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Craft.io in CrewAI
Craft.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Craft.io to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.