Bring Global Hiring
to CrewAI
Learn how to connect Remote 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 Remote MCP Server?
Connect your Remote account to any AI agent to streamline your global hiring, payroll, and compliance workflows. Remote provides a powerful RESTful platform for programmatically managing international teams, tracking employee data, and monitoring invoices across 150+ countries.
What you can do
- Company Orchestration — List and retrieve detailed metadata for all your registered company entities and their operational status.
- Global Talent Management — Access and monitor your global workforce, track employee profile data, and create new employee records programmatically.
- International Compliance Monitoring — List all countries supported by Remote to understand your global hiring capacity and requirements.
- Invoice & Financial Tracking — Access and monitor company invoices to ensure transparent and timely global payroll operations.
- HR Intelligence — Get a real-time overview of your international workforce and hiring trends using natural language commands.
How it works
1. Subscribe to this server
2. Enter your Remote API Key from your developer settings at remote.com
3. Start managing your global HR from Claude, Cursor, or any MCP client
Who is this for?
- Global HR & Finance Teams — monitor international payroll and employee data using natural language.
- Operations Managers — automate the onboarding of new global hires and track invoice statuses more efficiently.
- Developers — integrate real-time HR and compliance data into custom business dashboards.
Built-in capabilities (11)
Pass data as a JSON string. Add a new employee
Get specific company details
Get details for a specific employee
Get details for a specific invoice
List all registered companies
List all contractors
List employees for a company
List all employee expenses
List invoices for a company
List all countries supported by Remote
List all time-off requests
Why CrewAI?
When paired with CrewAI, Remote becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Remote 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
Remote in CrewAI
Remote and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Remote 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 Remote in CrewAI
The Remote 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
Remote for CrewAI
Every tool call from CrewAI to the Remote 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 get my Remote API Key?
Log in to your Remote account, navigate to the Developer or API Keys section in your dashboard, and generate a new key for your integration.
Which countries are supported?
Remote supports hiring and payroll in over 150 countries. You can use the list_supported_countries tool to see the full list in real-time.
Can I add employees programmatically?
Yes, the create_employee tool allows you to initialize new records for international hires directly from your AI agent, including job titles and locales.
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.