Bring Portfolio Management
to CrewAI
Learn how to connect AdaptiveWork (Clarizen) to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the AdaptiveWork (Clarizen) MCP Server?
Connect your AdaptiveWork (formerly Clarizen) account to your AI agent to unlock enterprise-grade project and portfolio management. From tracking high-level project health to creating granular tasks and managing resource availability, your agent handles complex workflows through natural conversation.
What you can do
- Project Portfolio Management — List and audit active projects, check health statuses, and retrieve executive summaries
- Task Orchestration — Create, assign, and update tasks across your project structure to ensure team alignment
- Resource Insights — List organization users and check assignments to optimize team capacity
- Advanced Querying (CZQL) — Run custom Clarizen Query Language commands to retrieve specific data subsets for reporting
- Portfolio Health — Quickly identify project bottlenecks or overdue milestones directly from your chat interface
How it works
1. Subscribe to this server
2. Enter your AdaptiveWork API Key and Server URL
3. Start managing your enterprise projects through Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — automate task creation and status reporting for large-scale initiatives
- PMO Leaders — audit portfolio health and resource utilization across departments
- Business Analysts — retrieve project data for financial reporting and performance analysis
- Team Leads — quickly update task progress and check team assignments without dashboard fatigue
Built-in capabilities (6)
You must provide a task name and its parent ID. Add a new granular task to a project or parent task structure in AdaptiveWork
Requires the Project ID. Retrieve detailed metadata and progress metrics for a specific AdaptiveWork project
Can filter by state or status in the tool response natively. Retrieve a list of active projects managed within the AdaptiveWork organization
Requires the Project ID. Retrieve the active task list associated with a specific project container ID
Retrieve the list of active organization users in AdaptiveWork to check resource assignments
Requires valid CZQL syntax. Execute advanced Clarizen Query Language (CZQL) commands for custom data retrieval
Why CrewAI?
When paired with CrewAI, AdaptiveWork (Clarizen) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AdaptiveWork (Clarizen) 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
AdaptiveWork (Clarizen) in CrewAI
AdaptiveWork (Clarizen) and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AdaptiveWork (Clarizen) 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 AdaptiveWork (Clarizen) in CrewAI
The AdaptiveWork (Clarizen) 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 6 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
AdaptiveWork (Clarizen) for CrewAI
Every tool call from CrewAI to the AdaptiveWork (Clarizen) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my AdaptiveWork API Key?
Log in to AdaptiveWork, go to Settings > Extensions. You can generate or retrieve your API key from the API section. Make sure your user profile has 'API User' permissions enabled.
What is CZQL?
CZQL (Clarizen Query Language) is a SQL-like language used to query the AdaptiveWork database. It allows for complex filtering, sorting, and data retrieval across all your entities.
Can I manage multiple project locations?
Yes! Use the list_projects tool to view all projects across your entire organizational structure, regardless of their location or department.
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.