When you source candidates from Codex as a recruiter or company team, Get on Board’s MCP server connects Codex to Talent Database so you can search Latin American tech professionals from your Codex session.
You can also give this whole page to your agent and ask it to install the server for you. The agent can follow the setup steps, add the MCP server, and then hand back the browser authorization step when Get on Board opens the OAuth flow.
Use the CLI setup path first. Codex stores MCP configuration in a shared config file, so the server you add from the terminal is also available in the Codex app.
Before you start
You need:
- Codex installed and signed in.
- A Get on Board recruiter account with access to an accepted company.
- The remote MCP server URL:
https://www.getonbrd.com/mcp.
Add the server from the Codex CLI
Open a terminal and run:
codex mcp add getonbrd --url https://www.getonbrd.com/mcp
codex mcp login getonbrd
The first command creates a Streamable HTTP MCP server named getonbrd. The second command opens the OAuth authorization flow in your browser.
When the browser opens:
- Sign in to Get on Board with your recruiter account.
- Select the company context Codex should use.
- Approve the requested MCP access.
After authorization, restart the Codex app or open a new Codex session so the tools are loaded.
Verify the connection
In Codex, ask:
Use the Get on Board MCP server to call whoami and confirm my active company.
Codex should return your Get on Board identity, the active company context, and the available MCP tools.
Then try a Talent Database search, for example:
Use Get on Board to find senior Python engineers in Mexico with English C1 who are available soon.
Optional: edit config.toml directly
If you prefer to edit Codex configuration yourself, add only the server URL:
[mcp_servers.getonbrd]
url = "https://www.getonbrd.com/mcp"
Then run:
codex mcp login getonbrd
Do not add an API key, client ID, client secret, or custom transport field. Codex and Get on Board complete Dynamic Client Registration and OAuth automatically in the browser.
What Codex can do with this server
See the Get on Board MCP Server overview for the full tool reference and example workflows.
If you need to reconnect
Use the same server name you chose when adding it. If you used getonbrd, you can reconnect with:
codex mcp logout getonbrd
codex mcp remove getonbrd
codex mcp add getonbrd --url https://www.getonbrd.com/mcp
codex mcp login getonbrd
If Codex does not show the Get on Board tools immediately after login, start a new Codex session or restart the Codex app.
Troubleshooting
Why did the Get on Board tools disappear?
Get on Board’s MCP access tokens last 2 hours, and the server does not issue a refresh token. When your token expires, Codex loses access to the Get on Board tools until you log in again. Follow “If you need to reconnect” above — expect this to happen periodically during a long session, it is not a bug. If authorizing again does not bring the tools back, wait a few minutes before you retry — several attempts in a row can hit our rate limits.
Run whoami first
Whenever you are not sure the connection is working, ask Codex to call whoami before anything else. It confirms your Get on Board identity, active company, granted scopes, and available tools, and it needs the least access of any tool to run. If whoami is the only tool Codex lists, your current authorization only grants the baseline “Confirm your Get on Board identity” permission — see the Talent Database permission below.
Use the exact server URL
Enter https://www.getonbrd.com/mcp exactly, matching “Before you start” above. A typo in the domain or the path sends your client to a server that is not ours, and the connection fails before OAuth starts.
Candidate search needs the Talent Database permission
The Talent Database search tool appears only when your authorization granted the “Search professionals in Talent Database” permission. The authorization screen lists the permissions your client asked for — you cannot add one there. So if whoami does not list that permission, remove the Get on Board connection in Codex and add it again, so it registers from scratch and asks for the permission.
More from Integrations and developer tools
Sign in with Google
