Bring Applicant Tracking
to Claude Code
Learn how to connect ApplicantStack to Claude Code 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 Subscribers
What is the ApplicantStack MCP Server?
The ApplicantStack MCP Server integrates your recruiting and onboarding workflows directly into your AI workspace. Efficiently manage your job listings, track candidate progress through custom stages, and streamline your hiring process using simple natural language.
Key Features
- Job Management — List all active and closed job openings, and retrieve full metadata for any specific listing.
- Candidate Tracking — Access your entire applicant database and filter by workflow stage or score.
- Workflow Automation — Move candidates between stages (e.g., from 'Interview' to 'Hired') and update their profiles instantly.
- Onboarding & Hires — Access onboarding data for new hires to ensure a smooth transition from applicant to employee.
- Secure Access — Uses private access tokens to safely interact with your organization's recruiting data.
Benefits for Teams
- Recruiters — Quickly check the status of candidates for multiple jobs without switching between tabs.
- Hiring Managers — Review candidate profiles and scores using AI-assisted summaries.
- HR Teams — Track hiring trends and ensure onboarding tasks are initiated for all new hires.
Built-in capabilities (7)
Verify ApplicantStack account connection
Get details for a specific candidate
Get details for a specific job
List all candidates
List all hires (onboarding)
List all job listings in ApplicantStack
Use stage field to move them in the workflow. Update candidate information or stage
Why Claude Code?
Claude Code registers ApplicantStack as an MCP server in a single terminal command. Once connected, Claude Code discovers all 7 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where ApplicantStack data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using ApplicantStack tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
ApplicantStack in Claude Code
ApplicantStack and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ApplicantStack to Claude Code 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 ApplicantStack in Claude Code
The ApplicantStack 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 Claude Code 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
ApplicantStack for Claude Code
Every tool call from Claude Code to the ApplicantStack 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 find my ApplicantStack API Token?
Log in to ApplicantStack, go to Settings, then Edit Settings. Your API token will be listed under the API section.
What is the subdomain?
The subdomain is the first part of your ApplicantStack URL (e.g., if your URL is mycompany.applicantstack.com, your subdomain is mycompany).
Can I move a candidate to a new stage?
Yes, use the update_candidate tool and provide the new stage name in the stage field to advance them in your workflow.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable