Skip to main content
Paste the setup prompt below into Codex. Your assistant edits its own MCP configuration and helps you connect to SeekOut.

​
Before you start

  • A SeekOut Recruit license and your SeekOut sign-in
  • A local task in the Codex desktop app or Codex CLI, with permission to edit your configuration

​
Connect with a prompt

1

Copy and send the setup prompt

Select Copy prompt, paste it into a local Codex task, and send it.

Add SeekOut MCP to my Codex configuration, preserve my other settings, and help me sign in.

Codex adds seekout-search to your user-level config.toml and preserves your other settings. If Codex requests permission to write the file, approve that change to continue.
2

Sign in to SeekOut

Complete the browser sign-in when Codex starts it. If the CLI is unavailable, open Settings → Plugins → MCP and select Authenticate for seekout-search after the configuration is saved.
3

Load the tools and verify

Restart Codex or open a new local task if requested. Ask Codex to run the credit check below. Saving the configuration is the first step; a successful tool call confirms the connection.
The desktop app and CLI share MCP configuration on the same Codex host. The default file is ~/.codex/config.toml; a custom CODEX_HOME changes its location. See OpenAI’s MCP guide.

​
Verify your first connection

Ask Codex to make a read-only SeekOut call:

Use SeekOut to check my remaining credits and summarize the result.

You are connected when Codex calls the SeekOut credit-check tool and returns your account’s credit information. If Codex only explains how to connect, follow the troubleshooting steps below. Then try a search:

Use SeekOut to find senior engineers in Austin with Kubernetes experience. Show the top five matches and explain why they fit.

​
Manual setup

Add the server from your terminal:
Or merge this entry into your user-level config.toml, updating the existing table if present:
Start browser sign-in from the terminal:
If the CLI is unavailable, use Authenticate in Settings → Plugins → MCP. Restart Codex and open a new local task after configuration changes. Terminal commands belong in your shell; the configuration file contains only TOML.

​
Troubleshooting

Use a local task with file-editing tools and send the complete setup prompt above. Approve the configuration-file write if requested. A hosted chat without access to your computer cannot change your local configuration.
Check that seekout-search is enabled and authenticated in Settings → Plugins → MCP. Restart Codex and start a new local task.If the CLI is available, run codex mcp get seekout-search on the same machine as your task. A remote host or different configuration directory needs its own setup. Project-specific configuration can also override your user configuration.
Select Authenticate in MCP settings, or ask Codex to run codex mcp login seekout-search. Keep the session running while you complete browser sign-in with the account that has your SeekOut Recruit license.
For account or service errors, see connection troubleshooting.