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:
https://app.hireloam.com/mcp
Claude
If Claude shows Custom connector limit reached, remove an unused connector or upgrade your Claude plan.
- Open Settings → MCP in Loam.
- In the Claude tab, copy the hosted server URL.
- Open Claude Desktop or Claude in your browser.
- Go to Customize → Connectors.
- Click +, then choose Add custom connector.
- Paste the hosted server URL and click Add.
- Click Connect.
- When the browser opens, sign in to Loam if needed, choose your workspace, and click Authorize.
- Enable Loam from Claude’s Connectors menu in a conversation.
For Team and Enterprise workspaces, an Owner may need to add Loam first from Organization settings → Connectors.
Claude Code
- Open Settings → MCP in Loam.
- In the Claude Code tab, copy the generated command:
claude mcp add --transport http loam https://app.hireloam.com/mcp
- Run that command in your terminal.
- Open Claude Code again and run
/mcp.
- Select loam and choose Authenticate.
- When the browser opens, sign in to Loam if needed, choose your workspace, and click Authorize.
Codex
- Open the MCP server setup flow in Codex.
- Enter these values:
| Field | Value |
|---|
| Name | loam |
| Transport | Streamable HTTP |
| URL | https://app.hireloam.com/mcp |
- Leave Bearer token env var, Headers, and Headers from environment variables blank.
- Click Save.
- When Codex prompts you to authenticate, finish the browser sign-in flow, choose your workspace, and click Authorize.
Cursor
- Open Settings → MCP in Loam.
- In the Cursor tab, click Add to Cursor.
- Approve the install inside Cursor.
- Click Authenticate.
- 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
- Open Settings → MCP in Loam.
- In the Other tab, copy the hosted server URL.
- Add Loam as a hosted MCP, remote MCP, or server URL connection in your client.
- Finish the browser sign-in flow and click Authorize.
What happens in the browser
After your client starts the connection:
- Loam opens a browser window or tab
- You sign in if needed
- You choose the workspace this client should access
- You review the requested scopes
- You click Authorize
- 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 [email protected]”
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
Especially powerful for founders already working in AI-native tools — check your pipeline without switching apps.
