> ## 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 Claude Code

> Paste a setup prompt into Claude Code to add SeekOut MCP to your user configuration, then sign in and verify the connection.

Paste the setup prompt below into Claude Code. Your assistant adds SeekOut directly to its user configuration so you can use it across projects.

Looking for the **Chat** tab or Claude.ai? Follow the [Claude connector guide](https://docs.seekout.com/mcp/connect/claude.md).

## Before you start

* A SeekOut Recruit license and your SeekOut sign-in
* A local session in the Claude Desktop **Code** tab or [Claude Code CLI](https://code.claude.com/docs/en/setup), 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 Claude Code session, and send it.

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

Set up SeekOut MCP for this local Claude Code installation. Make the configuration change using your tools, with user scope so it is available across my projects.

Use the Claude Code user configuration: .claude.json inside the current CLAUDE\_CONFIG\_DIR directory if that environment variable is set, otherwise .claude.json in my home directory. Merge a top-level mcpServers entry named seekout-search with this server configuration:

```json theme={null}
{"type":"http","url":"https://seekout-search-mcp.seekout.io/tools"}
```

If no entry exists and the Claude CLI is available, you can add it with: claude mcp add --transport http --scope user seekout-search [https://seekout-search-mcp.seekout.io/tools](https://seekout-search-mcp.seekout.io/tools)

Otherwise, edit the JSON directly, creating the file if missing. Update the existing server entry without duplicating it. Preserve unrelated settings and other MCP servers. Use native 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 JSON and report the configuration path and SeekOut entry. Tell me to restart the local Code session if needed, enter /mcp, select seekout-search, and choose Authenticate. Let me complete sign-in in my browser.

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.

Claude Code adds `seekout-search` to your user configuration and preserves your other settings. If it requests permission to write the file, approve that change to continue.

**2. Load the server and sign in**

Restart the local Code session if requested. Enter `/mcp` in Claude Code, select `seekout-search`, and choose **Authenticate**. Complete the SeekOut sign-in in your browser, then return to Claude Code.

**3. Verify the connection**

Run `/mcp` again to check the server status, then ask Claude Code to run the credit check below. Saving the configuration is the first step; a successful tool call confirms the connection.

> [!TIP]
>
> The default user configuration is `~/.claude.json`. User scope makes SeekOut available across projects, including local Code sessions in the desktop app. See [Claude Code's MCP configuration](https://code.claude.com/docs/en/mcp) and [shared desktop configuration](https://code.claude.com/docs/en/desktop#shared-configuration).

## Verify your first connection

Ask Claude Code to make a read-only SeekOut call:

Check my remaining SeekOut credits using the connected SeekOut tools.

Check my remaining SeekOut credits using the connected SeekOut tools.

You are connected when Claude Code calls the SeekOut credit-check tool and returns your account's credit information. Approve the tool call if Claude asks.

Then try a search:

Find five senior product managers in Seattle with fintech experience using SeekOut. Include a short explanation for each match.

Find five senior product managers in Seattle with fintech experience using SeekOut. Include a short explanation for each match.

## Manual setup

> **Configure SeekOut yourself**
>
> Run this in your terminal:
>
> ```bash theme={null}
> claude mcp add --transport http --scope user seekout-search https://seekout-search-mcp.seekout.io/tools
> ```
>
> Or merge this into your Claude Code user configuration, preserving existing settings and other entries in `mcpServers`:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "seekout-search": {
>       "type": "http",
>       "url": "https://seekout-search-mcp.seekout.io/tools"
>     }
>   }
> }
> ```
>
> Start a new local Claude Code session, enter `/mcp`, select `seekout-search`, and authenticate. To inspect the saved server from your terminal, run `claude mcp get seekout-search`.

## Troubleshooting

> **Claude explains the setup but does not edit the file**
>
> Paste the complete prompt into a local **Code** session with file-editing tools. Approve the configuration-file write if requested. For Claude's **Chat** tab, use the [Claude connector guide](https://docs.seekout.com/mcp/connect/claude.md).

> **SeekOut only appears in one project**
>
> Send the setup prompt above to configure SeekOut at user scope. If one project still uses an older endpoint, ask Claude Code to inspect that project's MCP settings: a local or project entry can override the user entry.
>
> See [Claude Code's MCP scopes](https://code.claude.com/docs/en/mcp#mcp-installation-scopes).

> **SeekOut is listed but needs authentication**
>
> Enter `/mcp` inside Claude Code, select `seekout-search`, and authenticate. Keep the session open until browser sign-in completes, then retry the credit check.

> **The Code tab does not show my connection**
>
> Start a new local Code session after saving the configuration. CLI configuration on your machine does not configure a cloud or remote machine. The setup prompt targets Claude Code's `.claude.json`, rather than the chat app's `claude_desktop_config.json`.

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.