Supercharge your AI with Troops. From Candidate Profile to Paid Time Entries.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Troops connects your AI agent directly to your HRIS backend. It manages everything from job posting creation (`create_job`) and candidate profile registration (`create_candidate`) to contract drafting, e-signature triggering, and time sheet submission.
You handle the entire talent lifecycle—recruiting, contracting, and payroll tracking—all through natural conversation.
What your AI can do
Create candidate
Registers a person into your system as a candidate record.
Create job
Creates an entirely new job opening with defined parameters.
Generate contract
Drafts and prepares a formal contract document based on specific employee data.
Retrieve a list of open jobs with list_jobs, or create brand-new job postings with specific details using create_job.
Register new people into your system using create_candidate, and fetch their full history and profile data instantly via get_candidate.
Draft a legally sound contract with generate_contract, then initiate the e-signature process by calling sign_contract.
Submit and manage time sheets for employees associated with active contracts using submit_timesheet.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 Compatible Gemini Waiting for input…
Troops MCP Server: 7 Tools for HR & Recruitment
Use these seven tools to manage the complete employee lifecycle—from creating job listings and tracking candidates, to drafting contracts and submitting payroll timesheets. Everything happens through your AI agent.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Troops on VinkiusCreate Candidate
Registers a person into your system as a candidate record.
Create Job
Creates an entirely new job opening with defined parameters.
Generate Contract
Drafts and prepares a formal contract document based on specific employee data.
Get Candidate
Retrieves the complete profile and history for an existing candidate ID.
List Jobs
Lists all job offers currently active in your system, allowing filtering by status.
Sign Contract
Initiates the electronic signature process for a generated contract.
Submit Timesheet
Submits and updates recorded hours worked against an employee's active contract.
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token from
cloud.vinkius.com. For OAuth-protected servers, expand Advanced
settings to add credentials.
Start a conversation
Open a new chat. The Troops integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Troops, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Troops. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 7 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Hiring means jumping between at least four different tabs and two separate logins.
Right now, onboarding a single candidate requires you to jump from your ATS (Applicant Tracking System) to an internal job board. You copy the job details into a spreadsheet, then log in to a contract generator to draft the paperwork. Finally, you email it out and wait for confirmation.
With Troops MCP Server, none of that happens manually. Your agent takes natural language input—'Set up the contract for candidate cand_987 for job job_001.' The server runs `generate_contract` and then prompts you to run `sign_contract`. You get the full execution in one chat window.
Troops MCP Server: Manage your entire workforce lifecycle.
The biggest time sink is tracking status. A candidate's progress, a job’s open date, and an employee’s hours are all in different silos. You have to ask multiple people, check multiple dashboards, and manually piece together the story of employment.
Now, your AI client keeps it straight. By exposing tools like `list_jobs`, `get_candidate`, and `submit_timesheet`, you get a single source of truth directly in your chat interface. You're not just getting data; you're getting an actionable workflow.
What your AI can actually do with this
You connect your AI agent straight into your HRIS backend with Troops. This MCP Server manages the entire employee lifecycle—from posting a job to submitting payroll hours—all through natural conversation. You handle recruiting, contracting, and time tracking without leaving your chat window.
Managing Job Listings:
You can check out all the open roles right now using list_jobs, which lets you filter results by current status. Need a new opening? Just call create_job and define every parameter for an entirely brand-new job posting. This keeps your listings updated fast.
Building Out Your Candidate Pipeline:
When someone applies, you register them into the system as a candidate record using create_candidate. You never have to worry about tracking down old data because you can grab the full profile and history for any existing ID instantly with get_candidate. This keeps your talent pool clean and up-to-date.
Processing Contracts:
The hiring process moves into gear when you draft a formal contract using generate_contract. You just feed it the specific employee data, and it spits out a legally sound document. Once that's ready, you initiate the e-signature flow by calling sign_contract, which triggers the entire electronic signing process for everyone involved.
Tracking Time & Pay:
Finally, when an employee is working against an active contract, you use submit_timesheet. This tool manages and updates recorded hours worked directly into their payroll records. It ensures every hour is logged correctly against the right agreement.
When your agent uses these tools together—say, calling list_jobs to find a role, then using create_candidate on a promising applicant, followed by get_candidate to review their history, generating the contract with generate_contract, getting signatures via sign_contract, and finally logging hours with submit_timesheet—you’re handling the entire employee lifecycle in one go.
You don't have to jump between five different systems just to hire someone or pay them.
019e38ff-4809-73c8-b74c-f56666f1ebc8 
Here's how it actually works
The bottom line is that you talk naturally to your AI client, and it handles the technical API sequence of interacting with Troops, so you never have to leave your chat window.
Subscribe to the Troops server and enter your unique API key.
Connect your preferred AI client (Claude, Cursor, etc.) to the MCP endpoint.
Start talking. Your agent translates your intent into specific tool calls—like 'List all open roles' or 'Sign contract for cand_123'—and executes them against your HR system.
Who is this actually for?
This is for HR Managers and Recruiters who spend too much time manually updating records across different systems. If you're tired of switching between the job board, the CRM, and the contract generator just to hire one person, this is for you. You need a single pane of glass where your AI agent can handle everything from first touchpoint to payroll data.
You use it to register new talent via create_candidate and draft contracts immediately using generate_contract, keeping the pipeline moving without manual copy-pasting.
You rely on this to get a full picture of compliance. Need to check all open roles? Call list_jobs. Need to verify candidate status? Use get_candidate.
You use it at the end of the employment cycle, running submit_timesheet and checking contract statuses through natural language prompts.
What Changes When You Connect
Need a full picture of all open roles? Call list_jobs. You get an immediate, filtered report without visiting the job board dashboard and clicking through filters. It's instant visibility into your current hiring capacity.
Ending the employment process is clean: Use generate_contract to draft the legal document, then follow up with sign_contract. Your agent handles that two-step workflow seamlessly, eliminating manual file transfers between systems.
Candidate data stays accurate. When you use get_candidate, your AI client gets a complete profile history—not just the last few entries. This ensures every hiring decision is based on full context, not partial views.
Keep payroll compliant by automating time entry. With submit_timesheet, you ensure hours are logged directly against active contracts, minimizing billing errors and making timesheet review fast.
Job creation is simple: Instead of navigating a form with 15 required fields, just ask your agent to call create_job. It handles the API payload construction for location, dates, and titles automatically.
See it in action
Hiring an urgent role.
The manager needs a new Product Manager immediately. Instead of logging into the job board to manually fill out every field, they tell their agent: 'Create a job for a PM in NYC.' The agent runs create_job, getting the ID back so the manager can then use that ID to track related candidate applications.
Bringing a new hire onboard.
The recruiter has signed the offer. They ask their agent, 'Get Alice's profile and generate her contract for job_001.' The agent runs get_candidate, pulls necessary details, then calls generate_contract using that data, saving hours of manual record-keeping.
End-of-quarter payroll cleanup.
The Ops team needs to reconcile time logs. They prompt their agent: 'Submit timesheets for all employees under contract ct_456.' The agent runs submit_timesheet, ensuring every worker's hours are logged and ready for the accounting system.
Checking candidate eligibility.
The hiring manager is reviewing a final-round candidate. They tell their agent, 'What's the full history for cand_987?' The agent calls get_candidate and returns the entire profile, letting the manager make an informed decision without checking multiple tabs.
The honest tradeoffs
Treating HR data like a simple database query.
User tries to combine job listing retrieval with candidate creation in one prompt: 'List jobs and also create a new candidate.' This forces the agent into an ambiguous state, potentially failing or creating orphaned records.
You have to separate those actions. First, run list_jobs if you need data. Second, call create_candidate when you are ready to register someone. Never mix record retrieval with record creation in one prompt.
Manually generating contracts and forgetting the signature step.
The user runs 'Generate contract for job job_001' and stops there, assuming the paperwork is done. The contract sits in draft status.
Remember that generate_contract only makes the document. To finish the process, you must explicitly call sign_contract. That tool triggers the actual e-signature workflow.
Assuming all data fields are available everywhere.
The user tries to submit a timesheet using a contract ID that doesn't exist in the system. The agent fails because submit_timesheet requires an active, valid contract reference.
Always check first. Use list_jobs or get_candidate to verify the IDs you need before attempting any write operation like submit_timesheet. Data integrity starts with verification.
When It Fits, When It Doesn't
Use this server if your core task involves creating, reading, updating, and deleting structured HR data—specifically jobs, candidates, contracts, or time entries. You must call it when you need to change the system state (e.g., calling create_job or sign_contract). Don't use this if all you want is a simple reminder or a calendar event; for those things, your AI client handles them natively. If you only need to read data that doesn't require an API call—like summarizing text from an email—then the server isn't necessary. But if you must pull candidate history (get_candidate) or confirm job status (list_jobs), this is the tool.
Questions you might have
How do I list all open jobs using the Troops MCP Server? +
You call list_jobs. This tool pulls a comprehensive list of current job openings, letting you check active roles without visiting the main dashboard. You can even filter this list by status.
What information does `get_candidate` retrieve? +
get_candidate retrieves all stored data for a specific candidate ID. This includes their full profile history and any associated records, giving you complete context on the person.
Does Troops MCP Server handle contract signing automatically? +
No. generate_contract only drafts the document. You must follow up by calling sign_contract, which is what actually triggers the e-signature process and finalizes the agreement.
How do I submit timesheets using the Troops MCP Server? +
To log hours, you use submit_timesheet. This tool requires an active contract ID to ensure that the submitted time sheets are accurately mapped against a live employment record for payroll purposes.
When I use `create_job`, what specific details must I provide for a job offer? +
You need to specify the role title, location, and expected start date. The tool requires these parameters so it can correctly structure the new listing in your HR system.
What data is captured when I run `create_candidate`? Does it save more than just a name? +
It captures comprehensive details, including full legal name, primary email, and candidate source. This initial registration allows you to build a complete profile for later use in contract generation.
Does `generate_contract` create the final legally binding document? +
No, it generates a structured draft using your company's template and specified job details. This output requires manual review before you trigger the electronic signature process via sign_contract.
How can I filter my results when listing jobs with `list_jobs`? +
You can filter by status, such as 'active' or 'draft'. This lets your agent pull only the job openings you need to see without going through every entry.
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.
We've already built the connector for Troops. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 7 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.