HN Showcase
Back to browse
100Hires MCP, 130 tools to run an ATS through LLM. Is 130 too many?

100Hires MCP, 130 tools to run an ATS through LLM. Is 130 too many?

by kravetsss·Jun 15, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidShip ItNiche Gem

130 MCP tools for ATS management when competitors ship 30-40.

Strengths
  • •130 tools is genuinely ambitious compared to competitor MCP servers with 30-40
  • •OAuth 2.1 with PKCE and per-user token scoping is properly implemented
  • •Remote server means zero installation required across all AI clients
Weaknesses
  • •Thin wrapper (~400 LOC) over existing REST API, not novel architecture
  • •Only useful if you're already using 100Hires ATS—not a standalone tool
Target Audience

Recruiting teams using AI assistants like Claude or Cursor

Similar To

GitHub MCP Server · Notion MCP · Zapier AI Actions

Post Description

Hi HN. I'm one of the co-founders of 100Hires ATS. We built an MCP server on top of our REST API.

I would love HN to weigh in on whether 130 tools are too many. Big competitors have 30-40

Some details:

Three layers, from the bottom up: - REST API v2: 87 endpoints, OpenAPI 3.0 spec, Bearer auth, public docs at 100hires.com/api - MCP server: 130 tools mapping roughly 1:1 to REST endpoints, hosted at mcp.100hires.com/mcp, ~400 LOC of wrapper code - ChatGPT plugin: thin wrapper on the MCP, OAuth handled by the plugin store

Auth on the MCP: OAuth 2.1 with PKCE and Dynamic Client Registration. Tokens scoped per user, 1-hour access tokens with auto-refresh, revoked when the user leaves the workspace. Tested in Claude Desktop, Claude Code, Cursor, VS Code, Codex, Windsurf, and Zed.

Available on the free trial (but rate-limited) and on all paid plans.

Similar Projects