AI assistant (MCP)
Noon + Claude
Noon exposes its AI recruiter as a remote MCP server. Add it as a connector in Claude or Claude Desktop — or with one command in Claude Code — sign in with your Noon account, and recruit from chat: paste a JD to start sourcing, review the feed, accept or reject candidates, and rewrite outreach sequences.
The Noon + Claude integration at a glance
How the integration works
In Claude, go to Settings → Connectors, add a custom connector named Noon with the server URL https://noon.fly.dev/mcp, and sign in with your Noon account via OAuth. In Claude Code, it's one command: `claude mcp add -s user -t http noon https://noon.fly.dev/mcp`, then `claude mcp login noon`. Claude then gets eight Noon tools: create a role from a job description and start autonomous sourcing, list your roles, view the candidate feed with match reasoning, accept or reject candidates, give feed-level feedback that restarts sourcing, and read or replace the LinkedIn + email outreach sequence for a role. Learn more about Noon's AI Sourcer and AI Outreach.
How Noon connects to Claude
Why teams pair Noon with Claude
Claude is Anthropic's AI assistant, and the Model Context Protocol (MCP) is its open standard for connecting external tools. Because Noon is itself an agentic recruiter, the pairing is natural: Claude handles the conversation, Noon does the recruiting work behind it — sourcing across the open web, evaluating candidates against your criteria, and running multi-channel outreach. Everything you do from Claude shows up in your Noon portal (and syncs onward to your ATS if you've connected one). See how Noon compares on the comparison hub or explore who Noon is built for.
An autonomous AI recruiter on top of your ATS
Noon + Claude FAQ
Does Noon have an MCP server for Claude?
Yes. Noon ships a remote MCP server at https://noon.fly.dev/mcp with OAuth sign-in. Add it as a connector in Claude or Claude Desktop, or in Claude Code with `claude mcp add -s user -t http noon https://noon.fly.dev/mcp` followed by `claude mcp login noon`.
What can Claude do with the Noon MCP connector?
Eight tools: create a role from a job description and start autonomous sourcing (create_role), list roles, view the candidate feed with Noon's match reasoning (get_feed), accept or reject candidates, give feed-level feedback that refines and restarts sourcing, and read or replace a role's LinkedIn + email outreach sequence.
Is it safe to sign in? How is access controlled?
The connector uses OAuth: you authorize Claude against your own Noon account, and every action is scoped to your workspace. Noon is SOC 2 Type II and GDPR compliant. You can review how data is handled in Noon's privacy policy.
Do actions taken from Claude show up in Noon?
Yes. Roles created, candidates accepted or rejected, and sequence edits made from Claude appear in your Noon portal immediately — and flow into your ATS if you've connected a native ATS integration.
Does this work in Claude Code?
Yes. Claude Code v2.1.186+ supports it directly with `claude mcp add` and `claude mcp login`; on older versions, run /mcp → noon → Authenticate.
Noon also integrates with Greenhouse, Ashby, Lever, Workable, Bullhorn, iCIMS, Loxo, and Gem. See all integrations.
See the Noon + Claude integration live — or explore the unlimited plan and enterprise options.