Bring Task Management
to CrewAI
Learn how to connect Sally 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 Sally MCP Server?
Connect your Sally instance to any AI agent and take full control of your API-first project management through natural conversation.
What you can do
- Projects — Create, list, and inspect projects with full metadata.
- Tasks — Full CRUD with priorities (P1-P4), statuses, labels, and assignees.
- Comments — Add comments to any task for collaboration and status updates.
- Kanban Board — Retrieve the aggregated board view showing tasks organized by status columns.
- Timesheets — Access timesheet reports with tracked hours and billing information.
- Profile — Verify your authenticated identity and workspace permissions.
How it works
1. Subscribe to this server
2. Enter your Sally API key, instance URL, and workspace slug
3. Start managing projects from Claude, Cursor, or any MCP client
Who is this for?
- Project Managers — create tasks, track progress, and review board status through AI commands.
- AI Developers — automate agent-driven task management in a system designed for human+agent collaboration.
- Operations Teams — monitor project velocity and timesheet data without switching tools.
Built-in capabilities (12)
Comments are visible to all project members. Add a comment to a task
Check Sally instance health
Create a new project
Optionally set priority (P1-P4), status, and labels. Create a new task in a project
Get the Kanban board view
Get the authenticated user profile
Get details of a specific project
Get full details of a specific task
Get timesheet report for the workspace or project
List all projects in the workspace
Optionally filter by project ID to see tasks for a specific project. List tasks, optionally filtered by project
Only provided fields are changed. Update an existing task
Why CrewAI?
When paired with CrewAI, Sally becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Sally 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
Sally in CrewAI
Sally and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Sally 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 Sally in CrewAI
The Sally 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
Sally for CrewAI
Every tool call from CrewAI to the Sally MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create a task with priority, labels, and status in one step?
Yes! Use create_task with the project ID, title, priority (P1-P4), status name, and comma-separated labels. The task is created instantly with all metadata.
How do I view my Kanban board from the AI agent?
Use get_board to retrieve the aggregated board data. Optionally pass a project ID to scope it to a specific project. Tasks are grouped by their status columns.
Does Sally require a hosted instance or cloud account?
Sally is a self-hosted, API-first project management system. You need your own Sally instance URL, an API key (atpm_ prefix), and your workspace slug to connect.
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.