# 100Hires [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/100Hires/mcp  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/100hires-2

## Description
Official MCP server for 100Hires ATS: candidates, jobs, applications, interviews, messages.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "100hires": {
    "command": "npx",
    "args": ["-y","100hires-2"]
  }
}
```

## Documentation

## What 100Hires MCP server does

The 100Hires MCP server connects an AI assistant to 100Hires, an applicant tracking system for recruiting teams. It exposes the 100Hires API through MCP tools, allowing compatible clients to work with recruiting data without a custom application or one-off API integration.

The server covers candidate records, job openings, applications, interviews, messages, and related hiring operations. It also includes tools for notes, evaluations, forms, questions, workflows, companies, users, and recruiting taxonomy such as sources, statuses, departments, categories, and tags. This places the integration in the Workplace & Productivity category for teams that want assistant-driven recruiting operations.

## How it works

100Hires MCP server is hosted at `https://mcp.100hires.com/mcp` and uses native HTTP transport. A compatible client connects to that endpoint, starts an OAuth flow in the browser, and then calls the available MCP tools against the connected 100Hires account.

Authentication uses OAuth 2.1 with Dynamic Client Registration and PKCE. Clients that support the MCP authorization flow can discover the required OAuth metadata automatically. Connected clients can be revoked from the 100Hires account under Settings, API, and Connected AI clients.

## Setup and configuration

No local installation is needed for clients that support HTTP MCP connections. Add the hosted endpoint as a custom connector or MCP server, then complete authentication in the browser. The README provides configurations for Claude Desktop, Claude Code, Cursor, Codex, and VS Code.

For clients that only support stdio, configure the third-party `mcp-remote` package as a bridge to the same HTTP endpoint. This approach uses `npx` to launch the bridge and does not replace the hosted 100Hires service.

## Tools and capabilities

The 100Hires MCP server provides tools to:

- List, create, update, tag, and message candidates; attach files and inspect candidate timelines.
- List applications and move them through pipeline stages, including advancing, hiring, rejecting, or transferring applications.
- List and create jobs, publish jobs to boards, manage hiring teams, and configure webhooks.
- Schedule interviews and retrieve interview details.
- Schedule or batch-send messages, manage notification emails, and create nurture campaigns.
- Create, read, update, and delete application notes and evaluations.
- Manage application forms, questions, pipeline stages, reusable workflow questions, companies, users, and taxonomy values.

The exact tool catalog is maintained in the provider’s MCP tool reference.

## Limitations and notes

The service is accessed through a hosted endpoint rather than a locally installed server. OAuth 2.1 is the documented authentication method, and the README does not describe environment-variable credentials or a manual API-key configuration. Older stdio-only clients require the `mcp-remote` bridge. Support documentation and the complete tool reference are available from 100Hires.

_Full upstream README: https://allmcps.com/mcp/100hires-2/readme_