Find the right person or role
Search results
Enter a search query to beginDETERMINISTIC IMPORT
Import historical records
Upload or paste CSV or JSON. Preview field mapping and issues before import. Plain text is not guessed into records.
Your account
Your recruiting records are private to your account.
Subscription
Payment status updates after a verified payment notification.
Only you and the administrators can see this conversation.
Manage accounts and subscription status. Disabling or deleting an account revokes access; billing remains managed separately.
Create a user account
Select a conversation
CONNECT YOUR AGENT
Your workspace, in your agent's tools
MCP gives Codex and other compatible agents secure access to this workspace's recruiting tools. Follow the quick setup below, then run a read-only check before making changes.
This address runs on your computer. Your MCP client must run on the same computer or have an explicitly configured network connection to it. A cloud client cannot reach this local address directly.
Connect MCP to Codex
The server is already hosted with this workspace. Configure Codex once using the URL and your private access token.
It grants access only to your signed-in workspace and expires 30 days after sign-in. Never paste it into chat or commit it to a repository.
2. Add the server from a terminal
Set the token in the same environment that launches Codex, then add the hosted Streamable HTTP server.
Restart Codex after adding the server. Run codex mcp list to confirm that recruiter_workspace is enabled.
Configure with config.toml instead
Merge this entry into your private ~/.codex/config.toml. If a recruiter_workspace entry already exists, update it instead of adding a duplicate.
Set RECRUITER_WORKSPACE_TOKEN in the environment that starts your MCP client. A terminal export only reaches processes launched from that terminal; an already running desktop app will not receive it.
Desktop setup without an environment variable
Use this alternative in your private user configuration, replacing the placeholder with your copied token. Use either this configuration or the environment-variable version above. This file contains a credential after replacement; keep it out of shared repositories.
Other MCP clients
Add an HTTP / Streamable HTTP server using the URL above and an Authorization header with the value Bearer <your copied token>. Field names vary by client. This service uses workspace tokens; it does not provide an OAuth sign-in flow.
Configuration reference: Official OpenAI MCP documentation.
Install the workspace Skill
Add reusable instructions for finding people and maintaining their project history.
- Download SKILL.md and review its instructions.
- For Codex, create
~/.agents/skills/recruiter-workspace/and place the downloadedSKILL.mdinside it. For another agent, use its documented skill directory. - Open a new task and select
recruiter-workspace, or invoke$recruiter-workspace. If the Skill does not appear, restart the client.
The Skill uses the MCP connection from step 1. Installing it alone does not connect a database or grant access. It covers searches, explicit record selection, versioned edits, and accurate communication history.
Installation reference: Official OpenAI skill documentation.
Verify access
Start with a read-only request before entering new records.
Checks initialization and tool discovery using your browser session. This does not install or verify your external client.
After configuring your client, confirm its tool list includes unified_search and list_records. Then ask it to list projects in your connected workspace.
Use $recruiter-workspace to list projects in my connected workspace. Do not change any records.| Task | Available tools |
|---|---|
| Find people and roles | unified_search, parse_batch_names |
| Inspect records and history | list_records, read_record, get_record_context |
| Save requested changes | create_record, update_record |
| Archive or restore | archive_record, restore_record |
MCP reads and writes use the same workspace database as this website. Connecting a client does not create a separate database. Edits need the latest record version; a queued task or draft is not a sent invitation. The service records communication history and does not send messages.
Troubleshooting
Connection refused or server unreachable
Keep the workspace service running. Check that the client can reach the displayed server URL. A local address refers to the machine running the client, including when that client runs remotely.
Unauthorized or expired token
Sign in again, copy the current access token, update your client's credential, and reconnect. Check that the environment variable is available to the actual client process.
The endpoint check passes, but my agent has no tools
The browser check only confirms this session can reach the endpoint. Check the client's server configuration, reload it, and inspect its tool-discovery errors. Installing the Skill does not install the MCP connection.
An edit reports a version conflict
Read the latest record, review changes made since the previous read, and retry the intended edit with the current version.