Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench • Explore Tool Discovery →

Live 16 Actions

Clockwork Recruiting MCP Server
for AI Agents

Connect your AI agent to StackOne's Clockwork Recruiting MCP server and give it ready-to-use MCP tools out of the box. Auth, tool execution, and security all managed.

Start Free Book Demo Read Docs →
Clockwork Recruiting logo
Clockwork Recruiting MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

16 Agent Actions

Create, read, update, and delete across Clockwork Recruiting — and extend your agent's capabilities with custom actions.

MCP Actions → Build Actions →

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Clockwork Recruiting MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Clockwork Recruiting tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Clockwork Recruiting call.

Tools Discovery →

What is the Clockwork Recruiting MCP Server?

A Clockwork Recruiting MCP server lets AI agents read and write Clockwork Recruiting data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Clockwork Recruiting MCP server ships with pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Clockwork Recruiting MCP Tools

Every action from Clockwork Recruiting's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Peoples

  • List People

    Find all People

  • Search People

    Find People using Search

Persons

  • Create Person

    POST /people

  • Get Person

    Find Person by ID

  • Update Person

    Update Person by ID

  • Delete Person

    Delete Person by ID

Projects

  • List Projects

    Find all Projects

  • Search Projects

    Search Projects

  • Get Project

    Find a Project by ID

Candidacies

  • List Candidacies

    Find all project candidacies

Candidacys

  • Create Candidacy

    Add candidacy to project

  • Get Candidacy

    Find Candidacy by ID

  • Update Candidacy

    Update candidacies

  • Delete Candidacy

    Delete selected candidacy who does not have any notes

Companies

  • List Companies

    Get all Companies

Companys

  • Get Company

    Find Company by ID

Clockwork Recruiting AI Agent Use Cases

Connect your AI agent to Clockwork Recruiting and help your team scale the recruiting operations they run by hand today.

Job Posting Distribution

Use StackOne to connect your AI agent to your ATS and job boards to automate job posting distribution.

View
GreenhouseLeverAshbySmartRecruitersWorkableJobviteiCIMSTeamtailor
Reference Check Automation

Use StackOne to connect your AI agent to your ATS, survey tools, and messaging systems to automate reference checks.

View
GreenhouseLeverWorkdayiCIMSSmartRecruitersAshbyTeamtailorSurveyMonkey
Offer Letter Generation

Use StackOne to connect your AI agent to your ATS, HRIS, and document management tools to automate offer letter generation.

View
GreenhouseLeverAshbyWorkdayBambooHRPersonioHiBobGusto
More Recruiting use cases

Set Up Your Clockwork Recruiting MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Clockwork Recruiting in under 10 lines of code.

MCP Clients

Claude Desktop setup guide
Claude Code setup guide
Cursor setup guide
Goose setup guide

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More Recruiting MCP Servers

JobAdder

246+ actions

Vincere

206+ actions

SmartRecruiters

164+ actions

Ashby

137+ actions

Manatal

130+ actions

Factorial

127+ actions

HiBob

123+ actions

All Recruiting MCP Servers →

Platform Resources

MCP Code Mode: Keeping Tool Responses Out of Agent Context

Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.

11 min

Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery

Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.

10 min

Indirect Prompt Injection Defense for MCP Tools: A Technical Guide

MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.

12 min

MCP vs A2A: Architecture, Security, and When to Use Each

MCP vs A2A: what each protocol standardizes, how they differ, their shared security risks including indirect prompt injection, and when to use one, both, or a hybrid architecture.

12 min

MCP vs API: What 200+ Connector Builds Taught Us

MCP wraps APIs, it doesn't replace them. After building 200+ connectors that serve both, here's when each approach wins.

14 min read

Clockwork Recruiting MCP Server FAQ

Does StackOne have a Clockwork Recruiting MCP server?
Yes. StackOne offers a hosted Clockwork Recruiting MCP server, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Clockwork Recruiting MCP server vs direct API integration — what's the difference?
A Clockwork Recruiting MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Clockwork Recruiting. A Clockwork Recruiting MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Clockwork Recruiting at runtime. StackOne provides both.
How does Clockwork Recruiting authentication work for AI agents?
Clockwork Recruiting authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Clockwork Recruiting account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Clockwork Recruiting MCP tools vulnerable to prompt injection?
Yes — Clockwork Recruiting MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Clockwork Recruiting agent and how do I avoid it?
Context bloat happens when Clockwork Recruiting tool schemas and API responses eat your Clockwork Recruiting agent's memory, preventing it from reasoning effectively. A single Clockwork Recruiting query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Clockwork Recruiting agent can access?
Yes — you can limit which actions your Clockwork Recruiting agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Clockwork Recruiting MCP server?
Yes — you can create custom agent actions for your Clockwork Recruiting MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Clockwork Recruiting's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Clockwork Recruiting MCP server?
Skip a Clockwork Recruiting MCP server if your integration is purely software-to-software — direct Clockwork Recruiting API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Clockwork Recruiting actions at runtime.
What AI frameworks and AI clients does the StackOne Clockwork Recruiting MCP server support?
The StackOne Clockwork Recruiting MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.

Start Free Book Demo