Loxo MCP Server

📚 Documentation: https://tbensonwest.github.io/loxo-mcp-server/

A Model Context Protocol (MCP) server that gives Claude direct access to the Loxo recruitment platform. Version 1.7.0 provides 34 tools covering the full recruiter workflow: searching and researching candidates, managing job pipelines, tracking activity and communication, working with companies, and maintaining candidate records. Tool descriptions guide Claude to surface recruiter intake notes and intel-rich activity history — so it can answer “where did we leave things with this candidate?” without you having to dig.

Installation

Option 0: Install via Smithery (easiest)

Install automatically for Claude Desktop via Smithery:

npx -y @smithery/cli install loxo-mcp-server --client claude

Option 1: Local Installation

# Clone the repository
git clone [repository-url]
cd loxo-mcp-server

# Install dependencies
npm install

# Build the project
npm run build

Option 2: Docker Installation

# Clone the repository
git clone [repository-url]
cd loxo-mcp-server

# Build the Docker image
docker build -t loxo-mcp-server .

# Or use Docker Compose
docker-compose build

Configuration

Copy the provided .env.example file to .env and fill in your values:

cp .env.example .env

Then update the .env file with your configuration:

LOXO_API_KEY=your_api_key
LOXO_DOMAIN=app.loxo.co
LOXO_AGENCY_SLUG=your_agency_slug

Required environment variables:

• LOXO_API_KEY: Your Loxo API key
• LOXO_AGENCY_SLUG: Your agency’s slug in Loxo
• LOXO_DOMAIN: (Optional) Defaults to ‘app.loxo.co’
• LOXO_DEFAULT_OWNER_ID: (Optional) Default Loxo user ID to set as owned_by_id on candidates created or updated via this server. Find your ID via loxo_list_users. Falls back to no owner if not set; overridden per-call by the owned_by_id arg.
• LOXO_DEFAULT_OWNER_EMAIL: (Optional) Default email for deal ownership. Used by loxo_create_deal when no owner_email arg is provided. Find emails via loxo_list_users.

Docker Configuration

When using Docker, environment variables are automatically loaded from your .env file via Docker Compose, or can be passed directly:

Using Docker Compose (recommended):

# Ensure your .env file is configured
docker-compose up

Using Docker directly:

docker run -i \