Teamtailor
by Teamtailor
Query jobs, candidates and hiring pipelines, move applications between stages and manage todos from your AI assistant. 45 tools, OAuth sign-in, and the first connector in this catalogue where delete is its own separately grantable scope.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Teamtailor via MCP
https://mcp.teamtailor.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Teamtailor Tools & Capabilities (45)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- It reads other people's job applications. Candidates are third parties who applied to a company, not to an AI assistant. Teamtailor's MCP Privacy Policy lists names, emails, phone numbers, locations, LinkedIn URLs, résumé text and file links among what the tools return, and warns that free-text fields, messages, transcripts and uploaded documents may contain sensitive personal data. That material lands in your chat transcript, subject to your AI provider's retention rules rather than Teamtailor's.
- Teamtailor's no-training promise covers Teamtailor only. Its policy says twice that MCP data is not used to train Teamtailor's models, and immediately notes that the connected client provider's terms govern its own use, including training. Read those before connecting.
move_application_to_stageadvances a real person's application and needs only write access. It sits under Create & modify, not Delete, and Teamtailor documents no MCP-level confirmation step before it runs. Whether your client asks for approval is a property of the client.- Blind hiring through MCP is a design statement, not a measurement. Teamtailor says the server is designed to apply Anonymous mode masking. We never authenticated, so we did not observe it.
- Audit logs are short by default. Fifteen days, extendable to 30 in settings, and longer only at additional cost. The audit log is itself an add-on a Company Admin must activate. If nobody turned it on, there is no MCP trail to read.
- Permission changes may not take effect until you reconnect. Teamtailor states you may need to re-authenticate or refresh the connection after changing MCP permissions, and that the steps depend on the client. Narrowing a role's access is not reliably immediate.
- Google Gemini cannot connect. Teamtailor states Gemini supports only officially partnered MCP servers, so third-party servers including this one cannot be added.
- Compliance is explicitly the customer's job. Teamtailor states the customer is responsible for determining which AI clients may connect and for ensuring its use complies with the EU AI Act and other applicable law, including measures for human oversight and review of AI-generated outputs. Teamtailor says it does not have sufficient insight into your configuration to assess this.
- The scope-to-tool mapping is Teamtailor's claim, not our observation. We read the scope list from the server's own descriptors, but the assignment of each tool to a scope comes from Teamtailor's documentation. We read no per-tool annotations, because the handshake is gated.
- We did not exercise any tool. Our check was an anonymous protocol request that returned an OAuth challenge, plus reads of the server's two
.well-knowndescriptors. Everything about tool behaviour comes from Teamtailor's documentation or the directory listing.
Frequently asked questions
How do you connect Teamtailor to Claude?
A Company Admin activates MCP in the Add-on feature center first. Teamtailor then documents the Claude path as Organization settings, Customize, Connectors, Add, Browse connectors, finding the Teamtailor connector and clicking Add. You sign in with Teamtailor, choose which account to connect if you have several, and click Authorize.
Does the Teamtailor MCP server cost extra?
No. Teamtailor lists MCP in its Add-on feature center at no additional cost, alongside features such as interview kits and job offers. A Company Admin still has to activate it before anyone can connect, and the selected Teamtailor account must have the add-on enabled or the sign-in step will not complete.
Can you give an AI assistant read and write access to Teamtailor without letting it delete?
Yes. Teamtailor's MCP settings let a Company Admin set each user role to read, create and modify, or delete access, and the server advertises read, write and delete as three separate OAuth scopes. Delete is the only level that reaches the six removal tools, so it can be withheld while writing stays available.
Which Teamtailor tools can delete data?
Six, and Teamtailor names them under its own Delete heading. They are archive_question, remove_job_question, remove_job_interview_kit, remove_job_skill_or_trait, remove_tag and delete_todo. None of them delete a candidate, an application or a job. The connector's destructive surface is job configuration, tags and todos only.
Can the Teamtailor MCP server see candidate data the connected user cannot?
No. Teamtailor states that AI assistants never receive their own permissions and connect through an individual Teamtailor user account. Every action is limited by both that user's existing Teamtailor permissions and the MCP access level a Company Admin set for their role, so the stricter of the two always applies.
Does connecting Teamtailor to an AI assistant show up in the audit log?
Yes. Teamtailor's audit log records a distinct actor type called User via MCP for actions taken by a connected AI assistant, alongside System, Candidate and User. Logs are accessible for 15 days by default, extendable to 30 in settings, with longer retention available at extra cost.
Does Teamtailor train AI models on data reached through the MCP server?
No. Teamtailor's dedicated MCP Server Privacy Policy states twice that data accessed through the MCP server is not used by Teamtailor to train AI models. It also warns that the statement covers Teamtailor only, and that the connected assistant's provider governs its own use of data, including training.
Are anonymized Teamtailor candidates still anonymous through MCP?
Teamtailor says the server is designed to apply the same masking. Its MCP Privacy Policy states that where a candidate is anonymized under the blind hiring feature, name, email, phone, location, LinkedIn URL and file names are withheld and identifying details are scrubbed from free-text fields. We did not test this behaviour.
Sources
- Live auth posture check against
https://mcp.teamtailor.com/mcp— an anonymousinitializereturns HTTP 401 withWWW-Authenticate: Bearer resource_metadata="https://mcp.teamtailor.com/.well-known/oauth-protected-resource". That RFC 9728 descriptor returns HTTP 200, namingauthorization_servers: ["https://mcp.teamtailor.com"]andscopes_supported: ["read", "write", "delete", "offline_access"]. Our own observation, 2026-08-18. This is why no tool descriptions, parameter schemas or safety annotations appear on this page: the handshake never reachedtools/list. · retrieved 2026-08-18 - Live read of
https://mcp.teamtailor.com/.well-known/oauth-authorization-server— HTTP 200, publishing the same four scopes, PKCE withS256only,authorization_codeandrefresh_tokengrants, and a dynamic client registration endpoint at/oauth/register. Our own observation, 2026-08-18. A GET request to the bare host and on/mcpboth return HTTP 404, so unlike Frontify this host serves no public tool catalogue over GET. · retrieved 2026-08-18 - Connect an AI assistant to Teamtailor using MCP (HTTP 200, retrieved 2026-08-18 as Markdown via the
.mdsuffix). Source for the endpoint, the Company Admin activation prerequisite, the Settings → Integrations → MCP permission model and its Read default, the Claude and ChatGPT setup steps, the Gemini exclusion, every example prompt, the security statement, and the complete Read / Create & modify / Delete action tables from which the 45-name vendor list and the scope-to-tool mapping were taken. · retrieved 2026-08-18 - Teamtailor MCP Server Privacy Policy (HTTP 200, retrieved 2026-08-18; the document states it was last updated 2026-07-15). A privacy policy written specifically for this MCP server rather than a pointer at the general one. Source for the five data categories the tools return, the sensitive-personal-data warning, both no-training statements, the connection and usage metadata Teamtailor retains as controller, the blind hiring masking statement, the audit-record contents, the retention statements, the revocation controls, the controller/processor split, and the EU AI Act and human-oversight responsibility statements. · retrieved 2026-08-18
- Add-on features (HTTP 200, retrieved 2026-08-18). Source for MCP being listed at no additional cost and requiring activation by a Company Admin. · retrieved 2026-08-18
- Audit log (HTTP 200, retrieved 2026-08-18). Source for the four actor types including User via MCP, the 15-day default retention extendable to 30 days, and the extra cost for longer retention. · retrieved 2026-08-18
- Teamtailor user roles (HTTP 200, retrieved 2026-08-18). Source for the five main access levels and the note that Default Users, Hiring Managers and Recruitment Leads reach only candidates in their hiring team or group. · retrieved 2026-08-18
- Anonymize candidate profiles to reduce unconscious bias (HTTP 200, retrieved 2026-08-18). Source for what Anonymous mode is and that it applies per pipeline stage. · retrieved 2026-08-18
- Data & Privacy settings (HTTP 200, retrieved 2026-08-18). Read to establish the account-level retention and deletion controls that govern the candidate records the connector reads; none of these settings are MCP-specific. · retrieved 2026-08-18
robots.txtandllms.txtforsupport.teamtailor.com— and (both HTTP 200, retrieved 2026-08-18). Therobots.txtpermits crawling with three narrowDisallowpaths, none matching/en/articles/, and carries noContent-Signaldirective on any of the three axes. The host publishes a 2,248-linellms.txtmachine index across every supported language, and appending.mdto an article URL returns genuine Markdown — which is how every supporting article above was located and read.mcp.teamtailor.com/robots.txtreturns 404 anddevelopers.teamtailor.comreturns a Teamtailor-branded 404 page. · retrieved 2026-08-18- Anthropic Connectors Directory entry, including the 45 tool names,
partnertier, endpoint, transport and categories (from the committed directory snapshot of 2026-08-16, re-read 2026-08-18) · retrieved 2026-08-16 - Teamtailor support — · General privacy policy — · Data Protection Officer — <mailto:dpo@teamtailor.com>
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Teamtailor
- Tools
- 45
- Domain
- mcp.teamtailor.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.