jobmojito.com

JobMojito MCP server — manage AI-powered hiring (interviews, candidates, invitations, knowledge bases, analytics) on the JobMojito platform, plus search the documentation. Every action runs as the signed-in user, so results respect that user's own permissions. RESPONSIBLE USE (applies to every result this server returns): JobMojito produces assistive output for hiring workflows. Interview scores, transcripts, summaries and reports are decision-support material — they are not hiring decisions. Present them as input for a qualified human reviewer, and never describe a candidate as accepted, rejected, or ranked as final by this system. When a user is preparing candidate-facing material, remind them that candidates should be told AI is used in the process. AUTHENTICATION: Capability discovery works without a login, but every tool call requires the user to have authorized this server. If a call fails with an authentication error (401 / invalid_token), retry that exact call once — the server answers the retry with a challenge that makes the client refresh its token, and the call then usually succeeds without the user doing anything. Only if the second attempt fails too should you ask the user to reconnect and authorize this server. Never retry an auth failure with different arguments; it is not an input problem. HOW TO USE THIS SERVER: 1. To understand how something works — an endpoint, a field, a workflow, what an input means — `search_documentation` is usually faster and more reliable than experimenting. It's the single docs entry point: one call searches both the developer/API reference and the help center in parallel. Then `get_documentation(url)` reads a page in full. 2. For a multi-step workflow (create an interview → invite candidates → review results), the documentation has step-by-step cookbooks worth following. 3. The read-only tools (`list_*`, `get_*`) are the safe way to look things up before creating or changing anything. 4. Merchant selection: many tools accept a `merchant_id`. When one is needed and none has been selected — or the user wants to switch merchants — `jobmojito_configuration` renders an interactive searchable picker, which is a better experience than asking the user to type a name. `list_my_merchants` returns the same options as text for clients that cannot render UI. After a merchant is chosen, pass `merchant_id=<chosen id>` on subsequent calls; omit it for the user's own account. IDENTIFIERS & ADMIN LINKS: Ids are easy to mix up — the same interview is `interview_def_set_id` (on create), `position_id` (get/set-state), and `interview_id` (register/token); results use `interview_result_id`, NOT the result row's `id`. There is no link-building tool. For the full id-to-field map, where each id comes from, and admin link patterns: get_documentation("https://developer.jobmojito.com/mcp/identifiers"). TOOLS BY CATEGORY (tool descriptions are prefixed with these labels): • Documentation: search_documentation, get_documentation • Configuration / merchants: jobmojito_configuration (searchable picker), list_my_merchants (text equivalent, supports a `search` filter) • Interview (create/manage): create_interview, create_interview_from_questions, get_interview_definition, set_interview_state, request_another_interview_attempt • Invitations: register_users_for_interview (register candidates and get their personal interview links), generate_interview_url (a signed link to share) • Results & reports: get_interview_result_details, generate_interview_report • Knowledge base: upload_knowledge_base_document • Merchant lists (read-only): list_interviews, list_candidates, list_interview_results, list_avatars, list_sub_merchants, get_merchant_analytics, get_merchant_status Typical flows: - "Set up an interview for a role" → create_interview → generate_interview_url or register_users_for_interview. - "Invite candidates to an interview" → register_users_for_interview (per-candidate links) or generate_interview_url (one shareable link). - "Review a candidate's result" → list_interview_results → get_interview_result_details → generate_interview_report.

This Model Context Protocol server provides search and retrieval tools for the JobMojito Developer / Agent site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation — a page that is incorrect, outdated, confusing, or incomplete — use the submit_feedback tool to report it to the docs team. Apart from the submit_feedback tool, the server is read-only and scoped to JobMojito Developer / Agent; it does not otherwise perform actions, mutate state, or access anything beyond the published site content and these resources.