Bring Hiring Pipeline
to Cursor
Learn how to connect Flatwork ATS to Cursor 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 Cursor?
Cursor's Agent mode turns Flatwork ATS into an in-editor superpower. Ask Cursor to generate code using live data from Flatwork ATS and it fetches, processes, and writes. all in a single agentic loop. 8 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Flatwork ATS in Cursor
Flatwork ATS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Flatwork ATS to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.