> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hireloam.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Setup

> Connect Loam to Claude, Claude Code, Codex, Cursor, or another MCP-compatible AI tool.

Loam's hosted MCP server lets you manage your hiring pipeline from tools like Claude, Claude Code, Codex, and Cursor without copying API keys into a local command. Use the setup flow in **Settings → MCP**, then sign in with Loam and approve access in the browser.

## Before you start

* Open **Settings → MCP** in Loam
* Use the client-specific setup tab that matches your AI tool
* Use the MCP endpoint shown in the environment you are testing

For production, the hosted endpoint is:

```text theme={null}
https://app.hireloam.com/mcp
```

## Claude

If Claude shows **Custom connector limit reached**, remove an unused connector or upgrade your Claude plan.

1. Open **Settings → MCP** in Loam.
2. In the **Claude** tab, copy the hosted server URL.
3. Open Claude Desktop or Claude in your browser.
4. Go to **Customize → Connectors**.
5. Click **+**, then choose **Add custom connector**.
6. Paste the hosted server URL and click **Add**.
7. Click **Connect**.
8. When the browser opens, sign in to Loam if needed, choose your workspace, and click **Authorize**.
9. Enable Loam from Claude's Connectors menu in a conversation.

<img src="https://mintlify.s3.us-west-1.amazonaws.com/matthewbusel/help/images/claude-custom-connector-loam.png" alt="Claude Add custom connector dialog with Loam as the name and https://app.hireloam.com/mcp as the remote MCP server URL" />

For Team and Enterprise workspaces, an Owner may need to add Loam first from **Organization settings → Connectors**.

## Claude Code

1. Open **Settings → MCP** in Loam.
2. In the **Claude Code** tab, copy the generated command:

```bash theme={null}
claude mcp add --transport http loam https://app.hireloam.com/mcp
```

3. Run that command in your terminal.
4. Open Claude Code again and run `/mcp`.
5. Select **loam** and choose **Authenticate**.
6. When the browser opens, sign in to Loam if needed, choose your workspace, and click **Authorize**.

## Codex

1. Open the MCP server setup flow in Codex.
2. Enter these values:

| Field     | Value                          |
| --------- | ------------------------------ |
| Name      | `loam`                         |
| Transport | `Streamable HTTP`              |
| URL       | `https://app.hireloam.com/mcp` |

3. Leave **Bearer token env var**, **Headers**, and **Headers from environment variables** blank.
4. Click **Save**.
5. When Codex prompts you to authenticate, finish the browser sign-in flow, choose your workspace, and click **Authorize**.

## Cursor

1. Open **Settings → MCP** in Loam.
2. In the **Cursor** tab, click **Add to Cursor**.
3. Approve the install inside Cursor.
4. Click **Authenticate**.
5. When the browser opens, sign in to Loam if needed, choose your workspace, and click **Authorize**.

If the button does not open Cursor, use the manual fallback URL shown in the same tab and paste it into **Cursor Settings → MCP**.

## Other MCP clients

1. Open **Settings → MCP** in Loam.
2. In the **Other** tab, copy the hosted server URL.
3. Add Loam as a **hosted MCP**, **remote MCP**, or **server URL** connection in your client.
4. Finish the browser sign-in flow and click **Authorize**.

## What happens in the browser

After your client starts the connection:

1. Loam opens a browser window or tab
2. You sign in if needed
3. You choose the workspace this client should access
4. You review the requested scopes
5. You click **Authorize**
6. Loam sends you back to the client automatically

Loam uses OAuth for this flow. API keys are not required for hosted MCP clients.

## Client notes

* **Claude Code**: the fastest path is the generated `claude mcp add --transport http ...` command from Loam.
* **Claude**: use a custom connector with the hosted `/mcp` URL. Claude Desktop and claude.ai remote connectors are configured through your Claude account.
* **Codex**: use a `Streamable HTTP` MCP server named `loam` with the hosted `/mcp` URL. Leave manual token and header fields blank because Loam uses OAuth.
* **Cursor**: the fastest path is the **Add to Cursor** button from Loam.
* **Older clients that only support local commands**: they may not yet work with the hosted OAuth flow.
* **Preview or local environments**: always use the MCP endpoint shown in the environment you are currently testing, not the production URL above.

## What you can do

| Category         | Actions                                                          |
| ---------------- | ---------------------------------------------------------------- |
| **Jobs**         | List jobs, get details, filter by status                         |
| **Applications** | List applications, get candidate details, filter by job or stage |
| **Sourcing**     | Add candidates with email, LinkedIn, and notes                   |
| **Feedback**     | Add notes, submit interview feedback                             |
| **Pipeline**     | Move candidates between stages                                   |
| **Search**       | Search candidates by name or email                               |

## Example prompts

* "What jobs do I have in Loam?"
* "Show me all candidates for the Senior Engineer role"
* "Move John to the Offer stage"
* "Add a new candidate to the Frontend role with email [jane@example.com](mailto:jane@example.com)"

## Troubleshooting

### The browser opened but the client did not connect

* Make sure the client supports **hosted MCP**, **remote MCP**, or **server URL** connections
* Confirm you finished the Loam authorization flow in the browser
* If you are using Cursor, try the manual fallback URL from **Settings → MCP**
* Re-open the connection from **Settings → MCP** and try again

### Claude says the custom connector limit was reached

* Remove an unused connector in Claude from **Customize → Connectors**
* Upgrade your Claude plan if you need more connector capacity
* After the limit is cleared, add Loam again with the hosted MCP URL from **Settings → MCP**

### I picked the wrong workspace

* Revoke the connection from **Settings → MCP**
* Reconnect and choose the correct workspace during authorization

### I still see the wrong connection in Loam

* Connections are shown per workspace in **Settings → MCP**
* Switch to the workspace you authorized and revoke the connection there
* Reconnect and choose the correct workspace during authorization

### The connection stopped working

* Check whether the MCP connection was revoked
* Reconnect if the session expired or the client cleared stored OAuth tokens
* If you are testing on preview or localhost, confirm the client still points at the correct MCP URL

<Tip>
  Especially powerful for founders already working in AI-native tools — check your pipeline without switching apps.
</Tip>