Skip to main content
The JobMojito MCP server exposes the JobMojito hiring platform — interviews, candidates, invitations, pre-screening, knowledge bases, analytics — plus documentation search as MCP tools. Point any MCP-capable client (Claude, or your own agent built on an MCP SDK) at it and the model can create interviews, invite candidates, pull results, and search these docs on your behalf. Every tool runs as the signed-in user: the server forwards your Supabase access token to the JobMojito API on each call, so results respect your own permissions. There is no anonymous access.
The MCP server is a convenience layer over the same HTTP API. For server-to-server integrations you usually want the API directly with a bearer token; use MCP when an AI agent should drive JobMojito interactively.

​
Endpoint

Connect your MCP client to: 
https://jobmojito.fastmcp.app/mcp
It speaks Streamable HTTP and is served directly (not behind a proxy auth gateway) so it can carry your Supabase token end to end.

​
Authentication (Supabase OAuth)

The server is an OAuth resource server; the authorization server is the JobMojito Supabase project. On first connection your client runs the standard OAuth flow:
  1. The client discovers the auth server from https://jobmojito.fastmcp.app/.well-known/oauth-protected-resource/mcp.
  2. You’re sent to the JobMojito sign-in / consent screen (hosted by Supabase at app.jobmojito.com) to log in and approve access.
  3. The client receives a token and attaches it to every MCP request.
  4. The server forwards that token to the JobMojito API for each tool call.
If a tool returns an authentication error (401 / invalid_token), the session isn’t signed in — re-authorize the connection and retry. See Authentication for how tokens map to environments and permissions.

​
Connect your agent

Pick your platform for step-by-step setup. Every path uses the same endpoint (https://jobmojito.fastmcp.app/mcp) and the OAuth sign-in above — no API key.

​
Merchant scoping

Most tools accept an optional merchant_id. Omit it to act on your own account; set it to act on behalf of a merchant you manage (agencies, resellers, sub-accounts).
  • MCP clients that can render UI get an interactive jobmojito_configuration picker — a searchable list of merchants. Pick one and it’s applied to subsequent calls.
  • Clients that can’t render UI use list_my_merchants (plain text, supports a search filter) and then pass merchant_id explicitly.

​
What’s next

  • Tools reference — the full tool inventory and the recommended docs-first calling pattern.
  • Identifiers & admin links — what each id means, which field wants it, and how to build admin app links. Read this if the model gets ids wrong.
  • Skills — reusable patterns and best practices for building reliable agent workflows on top of these tools.