Bring Task Management
to CrewAI
Learn how to connect Worksection 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 Worksection MCP Server?
Connect your Worksection account to any AI agent to automate your project management and team productivity workflows. Worksection provides a comprehensive set of tools for managing tasks, tracking time, and monitoring real-time project activities through natural conversation.
What you can do
- Project Lifecycle Management — List all projects, create new ones, and manage tasks across your entire organization programmatically.
- Time Tracking & Timers — Monitor active timers for team members and stop time trackers directly from the AI interface.
- Activity Monitoring — Retrieve a detailed event log of recent account activities to stay updated on project changes and completions.
- Stakeholder Collaboration — Access task comments, project members, and attached files to maintain a clear overview of team collaboration.
- Hierarchical Oversight — Navigate project folders and task sub-trees using simple natural language commands.
How it works
1. Subscribe to this server
2. Enter your Worksection Account Name (subdomain) and Administrative API Key
3. Start managing your projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — automate task status reports and monitor team timers without manual oversight.
- Operations Leads — track real-time activity across multiple projects and folders via natural conversation.
- Distributed Teams — streamline task coordination and ensure all project stakeholders are aligned programmatically.
Built-in capabilities (12)
Finish a task
Add new task
Get project info
Get full task info
Check running timers
List company users
List team on project
List tasks in project
List workspace projects
Get event log
Restore a task
Finish time tracking
Why CrewAI?
When paired with CrewAI, Worksection becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Worksection 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
Worksection in CrewAI
Worksection and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Worksection 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 Worksection in CrewAI
The Worksection 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
Worksection for CrewAI
Every tool call from CrewAI to the Worksection 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 Worksection Administrative API Key?
Log in to Worksection, navigate to Account Settings > API, and you will find your Administrative API Key listed there along with your account subdomain.
Can the AI stop active timers for team members?
Yes! Use the stop_timer tool and provide the task identifier (page) to stop any active time tracking for that specific task in your account.
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.