> ## Documentation Index > Fetch the complete documentation index at: https://docs.seekout.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect SeekOut to Codex > Paste a setup prompt into Codex to add SeekOut MCP to your local configuration, then sign in and verify the connection. 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](https://developers.openai.com/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. Set up SeekOut MCP for this local Codex installation. Make the configuration change using your tools. Use my user-level Codex config: config.toml inside the current CODEX\_HOME directory if that environment variable is set, otherwise .codex/config.toml in my home directory. Create it if missing. Merge this TOML entry: ```toml theme={null} [mcp_servers.seekout-search] url = "https://seekout-search-mcp.seekout.io/tools" enabled = true ``` If the entry already exists, update it without creating a duplicate table. Preserve unrelated settings, other MCP servers, and existing tool permissions. Use native Streamable HTTP with browser-based OAuth for SeekOut; remove conflicting stdio transport settings from this entry if present. Do not add API keys, bearer tokens, or client secrets, and do not print existing credentials. If the existing file is malformed, report the problem instead of overwriting it. Validate the saved TOML and report the configuration path and SeekOut entry. If the Codex CLI is available, run "codex mcp login seekout-search" to start browser sign-in. Otherwise, guide me to Authenticate for seekout-search in Settings → MCP servers. Let me complete sign-in in my browser. Tell me whether I need to restart Codex or open a new local task to load the server. Once SeekOut tools are available, use SeekOut to check my remaining credits. Only report the connection as working after that tool call succeeds; otherwise distinguish configuration saved from authentication or tool loading still pending. 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. > [!TIP] > > 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](https://developers.openai.com/codex/mcp). ## Verify your first connection Ask Codex to make a read-only SeekOut call: Use SeekOut to check my remaining credits and summarize the result. 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. Use SeekOut to find senior engineers in Austin with Kubernetes experience. Show the top five matches and explain why they fit. ## Manual setup > **Configure SeekOut yourself** > > Add the server from your terminal: > > ```bash theme={null} > codex mcp add seekout-search --url https://seekout-search-mcp.seekout.io/tools > ``` > > Or merge this entry into your user-level `config.toml`, updating the existing table if present: > > ```toml theme={null} > [mcp_servers.seekout-search] > url = "https://seekout-search-mcp.seekout.io/tools" > enabled = true > ``` > > Start browser sign-in from the terminal: > > ```bash theme={null} > codex mcp login seekout-search > ``` > > 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 > **Codex explains the setup but does not edit the file** > > 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. > **The server is saved, but SeekOut tools do not appear** > > 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. > **Sign-in did not finish or the session expired** > > 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](https://docs.seekout.com/mcp/reference/troubleshooting.md#connection-problems). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.