Bring Hiring Pipeline
to Claude Desktop
Learn how to connect Flatwork ATS to Claude Desktop and start using 8 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 Flatwork ATS MCP Server?
Connect your Flatwork ATS account to any AI agent and take full control of your recruitment pipeline and candidate management workflows through natural conversation.
What you can do
- Job Orchestration — List all open and closed job postings and retrieve detailed metadata, including hiring teams and job requirements programmatically
- Candidate Tracking — Manage your complete directory of applicants and retrieve detailed profiles and contact information programmatically
- Application Lifecycle — Monitor active job applications and update candidate hiring stages (Interview, Hired, Rejected) directly through your agent
- Applicant Discovery — Programmatically create new candidates in the system using external data to automate your sourcing pipeline
- System Monitoring — List configured webhooks to understand real-time data flows and ensure high-fidelity synchronization with your HR tools
How it works
1. Subscribe to this server
2. Retrieve your API Key from Flatwork ATS (Settings > API)
3. Start managing your hiring pipeline from Claude, Cursor, or any MCP client
No more manual status checking or digging through candidate lists. Your AI acts as your dedicated talent acquisition and recruitment coordinator.
Who is this for?
- Recruiters & HR Managers — instantly check application statuses and update hiring stages using natural language commands
- Talent Acquisition Teams — automate candidate registration from external sources and monitor job posting activity without leaving your workspace
- Hiring Managers — retrieve candidate profiles and job details through simple AI queries to prepare for interviews
Built-in capabilities (8)
Pass applicant data as a JSON string. Add a new candidate
Get applicant details
Get job details
List all applicants/candidates
List all job applications
List all job postings
List configured webhooks
Update application hiring stage
Why Claude Desktop?
Claude Desktop is the definitive way to connect Flatwork ATS to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Flatwork ATS in Claude Desktop
Flatwork ATS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Flatwork ATS to Claude Desktop 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 Flatwork ATS in Claude Desktop
The Flatwork ATS 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 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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
Flatwork ATS for Claude Desktop
Every tool call from Claude Desktop to the Flatwork ATS 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 Flatwork API Key?
Log in to your Flatwork account, navigate to Settings > API, and generate or copy your unique secret key.
Can I move a candidate to a custom hiring stage?
Yes! Use the update_application_status tool and provide the string name of your custom stage as defined in your ATS workflow.
How do I add new candidates found via LinkedIn?
Use the create_applicant tool and pass a JSON string containing the candidate's details like first name, last name, and email address.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.