Bring Job Management
to CrewAI
Learn how to connect Troops to CrewAI and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Troops MCP Server?
Connect your Troops account to any AI agent to streamline your recruitment and HR operations through natural conversation.
What you can do
- Job Management — List existing job offers or create new ones with specific locations and dates using
list_jobsandcreate_job. - Candidate Pipeline — Register new candidates and retrieve detailed profiles instantly with
create_candidateandget_candidate. - Contract Automation — Generate legal contracts for specific jobs and trigger electronic signature processes via
generate_contractandsign_contract. - Time Tracking — Submit and manage timesheets for active contracts to ensure accurate payroll using
submit_timesheet.
How it works
- Subscribe to this server
- Enter your Troops API Key
- Start managing your workforce from Claude, Cursor, or any MCP-compatible client
Who is this for?
- HR Managers — quickly list open positions and candidate details without switching tabs.
- Recruiters — automate the registration of new talent and contract generation.
- Operations Teams — streamline the submission of hours and contract signing workflows.
Built-in capabilities (7)
Register a new candidate
Create a new job offer
Generate a contract
Get candidate details
Can be filtered by status. List job offers
Sign a contract
Submit a time sheet
Why CrewAI?
When paired with CrewAI, Troops becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Troops 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
Troops in CrewAI
Troops and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Troops 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 Troops in CrewAI
The Troops 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 7 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
Troops for CrewAI
Every tool call from CrewAI to the Troops MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I see all currently published job offers?
You can use the list_jobs tool. You can also filter the results by status, such as 'published', to see only active listings.
Is it possible to register a new candidate directly through the AI?
Yes! Use the create_candidate tool by providing the candidate's first name, last name, and email address to add them to your Troops database.
How do I submit hours worked for a specific contract?
Use the submit_timesheet tool. You will need to provide the contract_id and a JSON array representing the daily hours worked.
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 →
Docker Hub
10 toolsManage Docker images on Docker Hub — list repositories, browse tags, create repos and search for community images from any AI agent.
CM.com
11 toolsReach customers on WhatsApp, SMS, RCS, and voice with a unified messaging platform built for conversational commerce.
FEMA
11 toolsAccess disaster and emergency data via OpenFEMA — track disaster declarations, housing assistance, and hazard mitigation directly through your AI agent.
OfficeRnD Flex
10 toolsManage flexible workspaces via OfficeRnD — track members, bookings, and billing directly from your AI agent.