Hirevoice MCP Connector
Connect Claude, ChatGPT or any MCP client to your Hirevoice workspace — setup, permissions, example prompts, and how to disconnect
Hirevoice runs a remote MCP server, so an AI assistant can work with your positions, candidates and interviews by asking Hirevoice directly — no export, no copy-paste, no separate credential to manage.
Connecting takes about a minute and is done by a company administrator.
Endpoint
https://mcp.hirevoice.com/mcpUse the URL exactly as written, with no trailing slash. …/mcp/ is
answered with a redirect that some clients refuse to follow, which shows up as
a connection that fails for no visible reason.
Connect
- Open Settings → Connectors in Claude, or run
claude mcp addin Claude Code. - Add a custom connector with the endpoint URL above.
- Click Connect. Hirevoice asks you to sign in, then shows exactly what the assistant is asking for. Read it before approving.
- Open Settings → Connectors → Add custom connector.
- Paste the endpoint URL above as the server URL.
- Click Connect, sign in to Hirevoice, and review the request before approving.
The server speaks streamable HTTP and authenticates with OAuth 2.1 —
authorization code with PKCE (S256) and dynamic client registration, so no
credential has to be issued to you by hand. Discovery is at
/.well-known/oauth-authorization-server on the same host.
There is no API key to copy and no secret to store. The assistant is issued its own short-lived credential, scoped to the workspace of the person who approved it, and it is renewed silently in the background.
Example prompts
Once connected, ask in your own words. These are representative rather than exhaustive — nothing here is a command syntax you have to learn.
Understand where a role stands
How many candidates do I have for the Senior Frontend Developer position, and how many have finished their interview?
Find someone specific
Find the candidates who interviewed for Customer Support last week and scored well on communication.
Read an interview back
Summarise Marta's interview for the Warehouse Operator role. What were her answers about shift availability?
Open a new role
Create a position for a part-time Barista in our Barcelona location, and tell me what you set up.
Check how hiring is going
How is our hiring funnel doing this month compared to last?
What an assistant can do
Every connection is scoped to one company. An assistant connected by an administrator at Acme can never see another customer's data — the boundary is enforced on every single request, not just at sign-in.
Within that boundary, capabilities fall into four groups. The consent screen names them in exactly these terms before you approve, and the last two are held apart deliberately: one leaves Hirevoice, and one cannot be undone.
| Group | What it covers |
|---|---|
| Read | Search and read positions, candidates, interviews and hiring metrics. |
| Write | Create and update positions, add candidates, and act on stuck interviews. |
| Messages candidates | Send outreach. This reaches a real person outside Hirevoice, and it cannot be recalled. |
| Destructive | Actions that cannot be undone, such as archiving a position. |
A viewer-role account cannot make an assistant write anything, even if the assistant tries: write and destructive tools are refused for viewers on every call.
Who can connect
Only company administrators. Granting an AI assistant access to a company's candidate data is an administrative act, not something an individual seat does on its own initiative. A non-administrator who reaches the consent screen is told to ask an administrator, and is not offered the choice.
Disconnect
Preferences → MCP settings in your Hirevoice dashboard lists every application currently connected, who connected it, and when it was last used.
Disconnecting is immediate. The assistant loses access on its very next request — there is no window during which a disconnected connector keeps working.
Any administrator can disconnect any connection in the company, including one another administrator created. That is deliberate: if someone leaves, their connection has to be cuttable without them.
The application name shown on the consent screen is supplied by the application itself and is not verified by Hirevoice. Treat it as a label, not as proof of identity — the callback address shown alongside it is the part worth recognising.
Privacy and data handling
Candidate data reached through the connector is covered by the same terms as the rest of Hirevoice, including our processing commitments with AI providers. Candidate data is not used to train models. See the privacy policy for the full text.
Connections, approvals and revocations are recorded in an audit trail that outlives the accounts involved, so "who granted what access, when, and who ended it" stays answerable.
Support
Something not working, or a connection you do not recognise? Write to support@hirevoice.com — and if it is a connection you do not recognise, disconnect it first and ask afterwards.