Bring Applicant Tracking
to Claude Desktop
Learn how to connect Workable to Claude Desktop and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Workable MCP Server?
Connect your Workable recruiting account to any AI agent and simplify how you manage your hiring pipelines, track candidates, and coordinate with your team through natural conversation.
What you can do
- Job Management — List all active and archived job openings and retrieve detailed job descriptions and requirements.
- Candidate Tracking — List and inspect candidates across all jobs, and drill down into specific profiles for experience and status.
- Direct Sourcing — Programmatically register new candidates to specific job openings to accelerate your hiring process.
- Team Coordination — List account members and recruiters to understand your hiring team structure.
- Ecosystem Overview — List linked accounts and verify your Workable instance configuration via AI.
How it works
1. Subscribe to this server
2. Enter your Workable Subdomain and API Key
3. Start managing your recruitment machine from Claude, Cursor, or any MCP client
Who is this for?
- Recruiters & HR Managers — quickly check candidate statuses and job metadata via simple AI queries.
- Hiring Managers — monitor the progress of specific pipelines and review new applicants without opening the dashboard.
- Operations Teams — automate candidate registration and track team activity levels directly from the workspace.
Built-in capabilities (7)
Register a new candidate to a job
Get details for a specific candidate
Get details for a specific job
List hiring team members
List candidates across all jobs
List active job openings
List connected accounts
Why Claude Desktop?
Claude Desktop is the definitive way to connect Workable to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 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
Workable in Claude Desktop
Workable and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Workable 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 Workable in Claude Desktop
The Workable 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 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
Workable for Claude Desktop
Every tool call from Claude Desktop to the Workable 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 the shortcode for a specific job?
Use the list_jobs tool. It returns a list of all your openings, each with its unique shortcode required for more detailed queries or actions.
Can I add a new candidate directly to a job via AI?
Yes! Use the create_candidate action. Provide the job shortcode along with the candidate's name and email to register them in your Workable pipeline.
Is it possible to see the recruiter assigned to an account?
Absolutely. Run the list_account_members query to retrieve the directory of all users and recruiters in your instance, including their roles.
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.