Bring Task Tracking
to CrewAI
Learn how to connect Workast to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Workast MCP Server?
Connect your Workast account to any AI agent to streamline your project management and task automation. Workast provides a powerful platform for organizing team workflows, tracking deadlines, and managing project backlogs directly within your existing communication tools.
What you can do
- Project & Space Orchestration — Organize your work using Spaces to group related task lists and projects for different teams.
- Task Lifecycle Management — Create, list, and update tasks with due dates, priorities, and detailed descriptions.
- Team Coordination — List and manage team members to assign responsibilities and monitor project progress programmatically.
- Metadata Synchronization — Access team-wide metadata and user profiles to keep your AI workflows aligned with your organization.
- Real-time Status Updates — Use natural language to get instant summaries of active spaces and task completion statuses.
How it works
1. Subscribe to this server
2. Enter your Workast API Token from your account preferences
3. Start managing your projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — automate the creation and tracking of team tasks via natural conversation.
- Team Leads — monitor progress across different spaces and channels without switching apps.
- Agile Teams — quickly update task statuses and manage backlogs using simple natural language commands.
Built-in capabilities (12)
Create a new space
Create a new task
Delete a task
Get my profile
Get space details
Get task details
Get team details
Get user details
List all Workast spaces
List tasks in a space
List team users
Update a task
Why CrewAI?
When paired with CrewAI, Workast becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Workast 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
Workast in CrewAI
Workast and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Workast 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 Workast in CrewAI
The Workast 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 12 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
Workast for CrewAI
Every tool call from CrewAI to the Workast 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 generate a Workast API Token?
Log in to Workast, go to your profile icon, select Preferences > API, and click 'Generate new token' to create your unique access credential.
What is a 'Space' in Workast?
A Space is a container for your task lists. It is typically used to organize different projects, client work, or team-specific channels within your workspace.
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.