Compatible with every major AI agent and IDE
What is the Infinity MCP Server?
Connect your Infinity account to any AI agent and manage projects through natural conversation.
What you can do
- Workspace Management — List all workspaces in your organization
- Board Navigation — Browse boards within workspaces and inspect their structure
- Folder Organization — Navigate folder hierarchies within boards
- Attribute Schema — View all custom attributes and fields configured on boards
- Item Management — List, create, update, and delete items (tasks/records) within boards
- Data Access — Read item field values and metadata
How it works
- Subscribe to this server
- Enter your Infinity Access Token
- Start managing projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — create tasks, update statuses, and organize boards through AI
- Teams — manage work items without switching to the dashboard
- Operations — automate task creation and tracking workflows
Built-in capabilities (12)
Verify Infinity API connectivity
Values must map to attribute IDs. Add a new item to a board
Get authenticated user info
List board attributes (fields)
List folders in a board
Supports filtering by folder. List all tasks/items in a board
List active webhooks for a board
List comments on an item
List boards in a workspace
List all workspaces
Delete an item from a board
Modify an existing item
Why CrewAI?
When paired with CrewAI, Infinity becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Infinity 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
Infinity in CrewAI
Infinity and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Infinity 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 | 4,000+ 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 Infinity in CrewAI
The Infinity 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
Infinity for CrewAI
Every tool call from CrewAI to the Infinity 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 and manage tasks through the AI agent?
Yes. Use create_board_item to add new items to any board, list_board_items to browse existing items, update_board_item to modify fields and status, and delete_board_item to remove items. Use list_board_attributes to see available fields.
Can I navigate workspaces, boards, and folders?
Yes. Use list_workspaces → list_workspace_boards → list_board_folders to navigate the hierarchy. Each level provides IDs needed for the next level and for item management.
Can I view custom fields and attributes on boards?
Yes. list_board_attributes retrieves all custom attributes (fields) configured on a board, including field type, options, and default values. This helps understand the data structure before creating or updating items.
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.
Explore More MCP Servers
View all →
BrandMentions
9 toolsMonitor social listening and brand mentions via BrandMentions — track keywords, manage projects, and list influencers directly from any AI agent.

Reflect
10 toolsEquip your AI to read, write, and explore your networked thought graph in Reflect Notes securely via their API.

Readwise
6 toolsEquip your AI to directly search, read, and retrieve your unified digital highlights, books, and Reader documents stored in Readwise.

Ironclad
10 toolsManage contracts, workflows, approvals, and counterparties via Ironclad CLM — launch, track, and search agreements directly from any AI agent.
