Bring Async Check Ins
to CrewAI
Learn how to connect Range to CrewAI and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Range MCP Server?
Connect your Range.co account to any AI agent and take full control of your team communication and check-in orchestration through natural conversation. Range provides a premier platform for keeping remote and hybrid teams synchronized, and this integration allows you to retrieve team metadata, monitor check-in updates (snippets), and track organizational objectives directly from your chat interface.
What you can do
- Check-in & Update Orchestration — List all managed updates and retrieve detailed metadata including snippet content programmatically.
- Team & User Lifecycle Management — Access and monitor your workspace teams and retrieve detailed user profile metadata directly from the AI interface.
- Objective & Goal Intelligence — Access organizational objectives to maintain a clear overview of team alignment and progress via natural language.
- Activity & Snippet Control — Retrieve specific snippets and check-in details to stay informed about daily team accomplishments.
- Operational Monitoring — Track system activity and manage workspace metadata using simple AI commands to ensure your team remains high-performing.
How it works
1. Subscribe to this server
2. Enter your Range API Key from your developer settings
3. Start managing your team check-ins from Claude, Cursor, or any MCP-compatible client
No more manual check-in reading or missed status updates. Your AI acts as a dedicated operations manager or team coordinator.
Who is this for?
- Engineering Managers — quickly retrieve daily updates and monitor team progress without switching apps.
- Product Leads — automate the retrieval of objective statuses and track feature delivery via natural conversation.
- Operations Teams — streamline the retrieval of user metadata and monitor organizational health directly within the chat.
Built-in capabilities (11)
Post a new standup update
Get details for a specific objective
Get details of a specific check-in snippet
Get details for a specific team
Get details of a specific update (check-in)
Get details for a specific team member
List all team goals
List team objectives
List all teams
Can be filtered by target_id or for_user_id. List team check-ins (updates)
List all users in the organization
Why CrewAI?
When paired with CrewAI, Range becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Range 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
Range in CrewAI
Range and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Range 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 Range in CrewAI
The Range 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 11 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
Range for CrewAI
Every tool call from CrewAI to the Range MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the recent check-ins for a specific user?
Yes! Use the list_updates tool with the for_user_id parameter. Your agent will respond with the most recent check-in snippets and status updates in seconds.
How do I find my Range API Key?
Log in to Range, go to Settings > Developer Settings > API Keys, and generate a new key for your account.
Can I see team objectives via the AI?
Yes, use the list_objectives tool to retrieve all active goals and targets configured in your Range 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.