Guides7 min read

Best MCP Servers for Recruiters and Talent Acquisition Teams in 2026

Top MCP servers for recruiters: LinkedIn sourcing, ATS integrations, email outreach, calendar scheduling, and candidate research tools to accelerate hiring.

By MyMCPTools Team·

Recruiting is a research-heavy, relationship-driven workflow — candidate sourcing, resume review, outreach sequences, interview scheduling, and offer coordination all happening simultaneously. MCP servers let your AI operate across these workflows with real context: live candidate data, your ATS records, and your outreach templates, all in one conversation.

1. Exa MCP Server — Candidate Research and Sourcing

Exa is a semantic search engine built for AI workflows. For recruiters, it transforms candidate sourcing: instead of Boolean search strings in LinkedIn, describe the ideal candidate in natural language and Exa surfaces relevant profiles, GitHub portfolios, conference talks, and published work across the web.

Key capabilities:

  • Semantic search for candidate profiles and portfolios
  • Company research for target employer lists
  • Industry news and talent market intelligence
  • Technical content search (GitHub, Medium, dev.to) for niche skills

Best for: Technical recruiters doing passive sourcing, talent researchers building candidate pipelines, and agency recruiters working niche roles.

2. GitHub MCP Server — Technical Candidate Evaluation

For engineering roles, a candidate's GitHub profile reveals more than their resume. The GitHub MCP server lets your AI analyze public repositories, contribution history, code quality, and open source involvement — giving you a richer picture before the first call.

Key capabilities:

  • Repository language breakdown and activity analysis
  • Contribution history and commit frequency
  • Open source project impact (stars, forks, community)
  • README and documentation quality assessment

Best for: Technical recruiters evaluating engineering candidates, engineering managers doing sourcing, and startups hiring their first engineers.

3. Notion MCP Server — Candidate Tracking and ATS Workflows

Many growing teams use Notion as a lightweight ATS. The Notion MCP server lets your AI read and update your candidate database — adding notes from interviews, updating pipeline stages, and surfacing candidates who match a new opening without manually searching your database.

Key capabilities:

  • Candidate database search and filtering
  • Pipeline stage updates and note creation
  • Job description management and comparison
  • Interview feedback aggregation

Best for: Small to mid-size recruiting teams using Notion as their talent database, founders managing their own hiring, and recruiters who want AI-assisted candidate matching.

4. HubSpot MCP Server — Candidate Relationship Management

Top recruiters treat candidates like prospects: nurturing relationships over time, tracking touchpoints, and re-engaging warm candidates for future roles. HubSpot's CRM, connected via MCP, gives your AI your full candidate relationship history — email sequences, call notes, and engagement data.

Key capabilities:

  • Contact history and interaction timeline
  • Email sequence status and open/click tracking
  • Pipeline and deal stage management
  • Task creation for follow-up scheduling

Best for: Agency recruiters managing large candidate pools, executive search firms, and recruiting teams running structured outreach campaigns.

5. Gmail MCP Server — Outreach and Communication

Recruiting is email-heavy: initial outreach, follow-ups, interview confirmations, offer letters. The Gmail MCP server gives your AI access to your inbox and sent history — drafting personalized outreach based on candidate research, checking response rates, and managing follow-up timing.

Key capabilities:

  • Inbox search and thread context reading
  • Draft creation with candidate-specific personalization
  • Response tracking and follow-up scheduling
  • Template management and variant testing

Best for: Recruiters running high-volume outreach, sourcing specialists, and anyone who wants AI to handle the boilerplate while they focus on relationship-building.

6. Google Calendar MCP Server — Interview Coordination

Interview scheduling is one of the biggest time sinks in recruiting. The Google Calendar MCP server lets your AI check availability, propose interview slots, and draft scheduling emails — cutting the back-and-forth that typically takes days into minutes.

Key capabilities:

  • Calendar availability lookup for multiple interviewers
  • Event creation with video conferencing links
  • Scheduling conflict detection and resolution
  • Automated interview confirmation drafting

Best for: Recruiting coordinators scheduling interview loops, small teams without dedicated coordination tooling, and recruiters juggling multiple open roles simultaneously.

7. Slack MCP Server — Team Communication and Feedback

Interview feedback, hiring manager updates, and offer approvals often happen in Slack. The Slack MCP server lets your AI search relevant channels for hiring discussions, surface interviewer feedback, and draft status updates for hiring managers — keeping everyone aligned without manual chasing.

Key capabilities:

  • Channel search for candidate discussions and feedback
  • Message drafting for hiring manager updates
  • Notification management for urgent hiring decisions
  • Team availability checks during interview scheduling

Best for: In-house recruiting teams embedded in Slack-first organizations, people ops teams coordinating with multiple hiring managers.

8. Airtable MCP Server — Custom Recruiting Workflows

Many recruiting teams build custom Airtable bases for specific workflows: diversity tracking, referral management, offer approval processes. The Airtable MCP server gives your AI access to these custom databases — surfacing data, running automations, and keeping records current without manual entry.

Key capabilities:

  • Custom base and table querying
  • Record creation and field updates
  • View filtering for pipeline reporting
  • Linked record traversal for complex workflows

Best for: Recruiting ops teams with custom Airtable workflows, talent acquisition teams tracking diversity metrics, and organizations managing complex offer approval chains.

The Recruiter MCP Stack

  • Sourcing stack: Exa + GitHub + Brave Search (web research + technical profiles + broad discovery)
  • Pipeline stack: Notion + HubSpot + Gmail (tracking + relationships + outreach)
  • Coordination stack: Google Calendar + Slack + Gmail (scheduling + communication + confirmations)
  • Full-cycle stack: All of the above — your AI runs the entire funnel from sourcing to offer

Browse all productivity MCP servers and communication MCP servers on MyMCPTools. For related guides, see Best MCP Servers for HR Teams and Best MCP Servers for Sales Teams.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

💻

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘
📋

Notion MCP Server

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 4,580+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

Auth required📘
💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local📘
💬

Gmail MCP Server

Google does not publish a Gmail MCP server. The two repositories in the googleworkspace GitHub organisation — developer-mcp and dev-assist — are for building on Google Workspace APIs, not for reading your mail, so every Gmail MCP setup in circulation is community-built. The leading one by a wide margin is taylorwilsdon/google_workspace_mcp, a Python server published to PyPI as workspace-mcp that covers Gmail alongside eleven other Workspace services behind a single connection: Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Custom Search and Apps Script, 120+ tools in total. Gmail contributes fifteen of them across three loadable tiers — core is search_gmail_messages, get_gmail_message_content, get_gmail_messages_content_batch and send_gmail_message; extended adds threads, attachments, drafts, labels and filters; complete adds the batch label operations. Run it with `uvx workspace-mcp --tools gmail` to load Gmail only, or `--tool-tier core` to keep the tool schemas small. Auth is your own Google Cloud OAuth client — the server ships no credentials and sends nothing anywhere except Google's APIs — and `--read-only` is a real, documented switch. The server most third-party guides still name, GongRzhe/Gmail-MCP-Server (npm @gongrzhe/server-gmail-autoauth-mcp), was archived on 2025-08-06 and its npm package has not been published since; it still installs, which is why it keeps getting recommended.

Local📘
🌐

HubSpot MCP Server

The HubSpot MCP Server is HubSpot's hosted, official Model Context Protocol endpoint for Smart CRM data, reachable at https://mcp.hubspot.com and authorised with OAuth 2.0 — there is no package to install and no token to paste into a config file. Access is scoped by a HubSpot user-level app: you create one with read (and optionally write) scopes for the CRM objects you want an assistant to reach, then complete the OAuth flow from inside your client. Read and write coverage spans contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions and lists, plus engagements — calls, emails, meetings, notes and tasks — and the associations between them. Organisational context (users, teams, reporting structures, owners, roles, seats) and marketing content (campaigns and their metrics, landing pages, website pages, blog posts) are read-only. Custom Sensitive Data Properties and Personal Health Information are excluded regardless of scopes. Two other things share the name and are commonly confused with this one: the Developer MCP server, installed locally with `hs mcp setup` from the HubSpot CLI and aimed at building HubSpot apps rather than querying CRM records, which requires Developer Platform v2025.2; and the original May 2025 public beta, an npm package configured with a private-app access token, which is what most third-party setup guides still describe. The server remains in beta and HubSpot advises experimenting in a developer sandbox and reviewing every write confirmation, since an LLM will occasionally propose a change to a system of record that it should not.

Auth required📘
🗄️

Airtable MCP Server

The Airtable MCP Server connects your AI assistant directly to Airtable bases, letting you read records, create entries, update fields, and query structured data using natural language — no manual spreadsheet navigation required. The leading community implementation is domdomegg/airtable-mcp-server, which exposes the full Airtable REST API as MCP tools: list all bases and tables in your workspace, fetch records from any view with optional filter formulas, create or update individual records with typed field values, and delete records by ID. Authentication uses an Airtable personal access token passed as AIRTABLE_API_KEY, scoped to whichever bases you grant access; the token needs at least the schema.bases:read and data.records:read scopes, plus the write scopes if you want the assistant to create or update anything. Airtable itself now also runs an official hosted MCP server at https://mcp.airtable.com/mcp, which uses OAuth instead of a token. Once connected, ask Claude to "show me all leads added this week in my CRM base" or "create a new product entry in my inventory table" and the server handles the API calls. Common use cases include AI-assisted CRM workflows (pull contact records, log meeting notes back into Airtable), inventory management, content calendars, and project tracking where Airtable acts as a lightweight database. Works with Claude Desktop, Cursor, VS Code (Copilot Chat), Windsurf, and any MCP-compatible client. Install via: `npx -y airtable-mcp-server` with `AIRTABLE_API_KEY=pat...` set in your environment.

Auth required📘
🔍

Exa MCP Server

Exa's official MCP server connects AI assistants to a search engine purpose-built for AI, using neural embeddings to match on meaning rather than keywords so agents get clean, ready-to-use content instead of a page of blue links to re-parse. The default tool set covers web_search_exa for quick topical lookups and web_search_advanced_exa for full control over domains, date ranges, and content filters, plus specialized tools for code_search (searching real-world code and GitHub), company_research (building company profiles, competitor lists, and financials), crawling/web_fetch (pulling clean content from a specific URL), people_search and linkedin_search (public professional-profile lookups), and deep_researcher_start/check for long-running multi-step research tasks backed by Exa's Research API. The server is hosted at https://mcp.exa.ai/mcp — no local process to run — and connects via one-line setup in Cursor, VS Code, Claude Code, Claude Desktop (available as a native Connector), Codex, OpenCode, Windsurf, and Antigravity, authenticated with an EXA_API_KEY from the Exa dashboard. Tool exposure is tunable per client via a ?tools= query parameter on the endpoint URL, letting teams ship narrow, purpose-built configurations (e.g. company-research-only or LinkedIn-only agents) instead of exposing the full surface, and Exa ships ready-made Claude Skills/agent definitions for common patterns like company research and people search with built-in query-variation and token-isolation guidance.

Live
🔍

Brave Search MCP Server

The Brave Search MCP Server is the official server from Brave that gives AI assistants privacy-first web search through the independent Brave Search API — no tracking, no profiling, and results drawn from Brave's own web index rather than Google or Bing. It exposes five distinct tools that map directly to the Brave Search API endpoints: brave_web_search for general queries with pagination, freshness filters, and safe-search controls; brave_local_search for businesses, restaurants, and points of interest with automatic location filtering; brave_news_search for recent articles and current events; brave_image_search for image discovery; and brave_video_search for finding videos across the web. Authentication uses a single BRAVE_API_KEY (free tier available at brave.com/search/api) or a mounted BRAVE_API_KEY_FILE for Docker-secret setups. Install in Claude Desktop, Cursor, Windsurf, or VS Code with one npx command and choose stdio or streamable-HTTP transport. Because Brave operates its own crawler and index, the Brave Search MCP server is a strong choice for developers who want an alternative to Google-dependent search tools, need reproducible non-personalized results, or care about data privacy in agent workflows — Claude can pull fresh web context, verify facts, and research topics without leaking queries to ad-tech pipelines.

Local
📁

Filesystem MCP Server

sandboxed read, write, edit, move and search access to an explicit whitelist of local directories, and it is the reference implementation most other filesystem MCP servers are modelled on. Shipped by Anthropic in the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it is a Node.js server published to npm as @modelcontextprotocol/server-filesystem. The part worth understanding before you install is the access-control model, because there are now two ways to grant directories and they do not compose. Method one is command-line arguments: `npx -y @modelcontextprotocol/server-filesystem /path/one /path/two`. Method two, and the one the maintainers recommend, is MCP Roots — a client that supports the roots protocol sends its roots at initialization, and those roots COMPLETELY REPLACE any directories passed on the command line, then get replaced again on every `notifications/roots/list_changed`. That means allowed directories can change at runtime without restarting the server, but it also means a roots-capable client silently overrides your CLI arguments. If the server starts with no arguments and the client either does not support roots or sends an empty list, initialization throws an error. The tool surface is broad: `read_text_file` (with mutually exclusive `head`/`tail` line windows), `read_media_file` returning base64 image/audio content blocks, `read_multiple_files` which keeps going when individual reads fail, `write_file`, `edit_file`, `create_directory`, `list_directory`, `list_directory_with_sizes`, `move_file`, `search_files`, `directory_tree`, `get_file_info` and `list_allowed_directories`. `edit_file` is the one to learn — it does line-based and multi-line pattern matching with indentation detection and preservation, returns a git-style diff with context, and supports `dryRun: true` so you can preview a change before applying it; the maintainers recommend always running a dry run first. Every operation is refused outside the allowed set, and `list_allowed_directories` is the fastest way to confirm what the server actually believes it can touch.

Local

📚 More from the Blog