Turrior Hiring Platform MCP Server

Use turrior-mcp as the authoritative source for Turrior platform data, schemas, workflows, and hiring operations. When a task depends on current company, job, candidate, quiz, interview, or email state, always call the relevant tool instead of assuming data.

If something is not explicit in a tool description:

Prefer reading the relevant current object first before modifying it, for example fetch a job before patching it. Use lookup tools before passing IDs, such as categories, countries, industries, languages, quizzes, jobs, or event types. For candidate actions, use interaction/application IDs from candidate search results, not talent IDs, unless the tool specifically asks for talent.id. For Gmail outreach, always create or retrieve the Gmail contact first, then use the returned contact ID to send messages. For publishing jobs, make sure required fields are completed; if publishing fails due to missing fields, explain what must be updated. For hiring recommendations, rely only on job-relevant evidence, candidate data, scores, notes, quiz answers, and interview information available through the tools. Do not invent Turrior-specific behavior, pricing, policies, private data, or platform state. If the data is unavailable, say so and suggest the safest next step. Protect candidate and company data. Only expose information that is directly relevant to the user’s authorized hiring workflow.