The MCP Teamtailor is a Model Context Protocol (MCP) server that provides a simple integration with the [teamtailor
If you already use MCP, the mcp mcp server is the piece that lets your assistant work with it directly. The MCP Teamtailor is a Model Context Protocol (MCP) server that provides a simple integration with the teamtailor api.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
teamtailor_list_candidates — List and filter candidatespageSize — The size of the page response (string, optional)page — The page number to retrieve (string, optional)filter.createdAfter — Filter candidates created after a specific date (string, optional)filter.createdBefore — Filter candidates created before a specific date (string, optional)filter.updatedAfter — Filter candidates updated after a specific date (string, optional)filter.updatedBefore — Filter candidates updated before a specific date (string, optional)teamtailor_get_candidate — Get a single candidate by their idcandidateId — The id of the candidate to retrieve (number, required)Configuration is passed through the environment: TEAMTAILOR_URL, TEAMTAILOR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — teamtailor_list_candidates, pageSize, page and 6 more — is a fair guide to whether it matches your workflow. It is maintained by crunchloop; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| teamtailor_list_candidates | List and filter candidates. |
| pageSize | The size of the page response (string, optional) |
| page | The page number to retrieve (string, optional) |
| filter.createdAfter | Filter candidates created after a specific date (string, optional) |
| filter.createdBefore | Filter candidates created before a specific date (string, optional) |
| filter.updatedAfter | Filter candidates updated after a specific date (string, optional) |
| filter.updatedBefore | Filter candidates updated before a specific date (string, optional) |
| teamtailor_get_candidate | Get a single candidate by their id. |
| candidateId | The id of the candidate to retrieve (number, required) |
{
"mcpServers": {
"teamtailor": {
"command": "npx",
"args": [
"-y",
"@crunchloop/mcp-teamtailor"
],
"env": {
"TEAMTAILOR_URL": "https://api.teamtailor.com/v1",
"TEAMTAILOR_API_KEY": "XXXX"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TEAMTAILOR_URL | Endpoint or connection string the server talks to. | Yes |
| TEAMTAILOR_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.