# Breezy HR MCP MCP Server > **Breezy HR MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Breezy HR MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/breezy-hr-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Breezy HR manages the recruiting lifecycle, from job openings to candidate hiring decisions. Create positions, source candidates from resumes, review applications and assessments, manage candidate documents and scorecards, track hiring pipelines, communicate with applicants, and analyze recruitment activity. --- ## Details - Server ID: `breezy-hr-mcp` - Version: 0.25.0 - Tools: 55 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Breezy HR MCP has to be in the toolset first. In order: 1. Add Breezy HR MCP to your toolset at https://mewcp.com/mcp/breezy-hr-mcp 2. Connect your Breezy HR MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (55) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `get_user` _(read)_ — Get the currently authenticated Breezy HR user. - `get_user_details` _(read)_ — List the companies the authenticated Breezy HR user belongs to, with each company's ID, name, friendly_id and its position and member counts. Use… - `list_companies` _(read)_ — List all companies available to the authenticated Breezy HR user. Returns company IDs needed for other API calls. - `get_company` _(read)_ — Get details for a specific Breezy HR company by ID. Use list_companies first to get available company IDs. - `list_pipelines` _(read)_ — List all pipelines for a Breezy HR company. Returns an array of pipeline objects each containing a stages array. Stage id values (e.g. "applied",… - `get_pipeline` _(read)_ — Get the stages for a specific pipeline. Returns { pipeline_id, stages: [...] }. Use list_pipelines first to get pipeline IDs and see all pipelines at once.… - `list_company_questionnaires` _(read)_ — List questionnaires available for a Breezy HR company. - `get_company_questionnaire` _(read)_ — Get details for a specific company questionnaire including its questions. - `list_company_templates` _(read)_ — List email templates available for a Breezy HR company. - `get_company_template` _(read)_ — Get details for a specific company email template. - `get_candidate_custom_attributes` _(read)_ — Get the custom attribute definitions for candidates in a Breezy HR company. - `get_position_custom_attributes` _(read)_ — Get the custom attribute definitions for positions in a Breezy HR company. - `list_positions` _(read)_ — Use this when the user asks about their jobs or job openings ("what jobs do I have open", "my line cook job"), or to find the position_id another tool needs.… - `get_position` _(read)_ — Get details for a specific position (job opening) in Breezy HR. - `get_position_team` _(read)_ — Get team members assigned to a specific position in Breezy HR. - `get_position_stream` _(read)_ — Get the activity stream for a specific position in Breezy HR. Returns one page of 30 events, newest first. To read further back, call again with skip set to… - `get_position_custom_fields` _(read)_ — Get custom fields defined on a specific position in Breezy HR. - `add_position` _(write)_ — Create a new position (job opening) in Breezy HR. - `update_position` _(destructive)_ — Use this when the user wants to change a job that already exists, such as its title, description, pay or location. Updates an existing position in Breezy HR.… - `set_position_state` _(write)_ — Use this when the user wants to open, close or archive a job, for example once the role is filled. Changes the state of a position (e.g. publish, close,… - `update_position_custom_field` _(destructive)_ — Update a custom field value on a position. Use get_position_custom_fields to see available fields. - `list_candidates` _(read)_ — Use this to read who applied to a job for your own reasoning, such as counting applicants or finding a candidate by name. Lists candidates for a position in… - `search_candidates` _(read)_ — Use this when you have a candidate's email address and need to find them across every job in a company. Searches by email address only; to find a candidate by… - `get_candidate` _(read)_ — Get full details for a specific candidate including work history, education, social profiles, cover letter, and custom attributes. Use this when you need… - `get_candidate_meta` _(read)_ — Get rich metadata for a candidate including notes, scorecards, tasks, interviews, documents, and conversation history. - `get_candidate_stream` _(read)_ — Get the activity stream for a specific candidate including notes, stage changes, and other events. Returns one page of 50 events. To read further back, call… - `get_candidate_conversation` _(read)_ — Get the conversation history for a specific candidate including messages between the candidate and hiring team. - `get_candidate_resume` _(read)_ — Use this to read a candidate's resume. Returns the resume's text for PDF resumes, the most common format; for other formats, only the file type and size, since… - `get_candidate_documents` _(read)_ — Get documents attached to a specific candidate. - `get_candidate_questionnaires` _(read)_ — Get questionnaires and responses for a specific candidate. - `get_candidate_assessments` _(read)_ — Get third-party assessment results for a specific candidate. - `get_candidate_background_checks` _(read)_ — Get background check results for a specific candidate. - `get_candidate_custom_fields` _(read)_ — Get custom field values for a specific candidate. - `add_candidate` _(write)_ — Use this when the user wants to add someone they found or were referred to as a candidate for a job and has no resume file. Creates a new candidate on a… - `update_candidate` _(destructive)_ — Update fields on a candidate. Can change name, email, phone, summary, headline, address, tags, social profiles, source, and cover letter. - `update_candidate_custom_field` _(destructive)_ — Update a custom field value on a candidate. Use get_candidate_custom_fields to see available fields and get_candidate_custom_attributes (company level) for… - `update_candidate_education` _(destructive)_ — Update education for a candidate. Requires school_name at minimum. Optional: degree, field_of_study, start_year, end_year. - `update_candidate_work_history` _(destructive)_ — Update work history for a candidate. Requires company_name at minimum. Optional: title, summary, start_year, start_month, end_year, end_month. - `update_candidate_custom_attribute` _(destructive)_ — Set a custom attribute on a candidate. Custom attributes are name/value string pairs. - `move_candidate` _(write)_ — Use this when a candidate should be considered for a different job. Moves a candidate from one position to another. Requires the target position ID and target… - `set_candidate_stage` _(write)_ — Use this when the user wants to move a candidate forward or back in the hiring process, for example to interviewing, offer or hired, or to reject them… - `post_candidate_note` _(write)_ — Use this when the user wants to record feedback or a private note about a candidate, such as interview impressions. Adds an internal note to a candidate's… - `post_candidate_message` _(write)_ — Use this when the user wants to contact a candidate, for example to ask their availability, invite them to interview or follow up. Sends a message to a… - `add_candidate_scorecard` _(write)_ — Use this when the user wants to rate a candidate or record a hiring vote ("strong yes on Elena"). Adds a scorecard rating for a candidate. Score must be one… - `send_candidate_questionnaire` _(write)_ — Use this when the user wants a candidate to answer screening or follow-up questions. Sends a questionnaire to a candidate. Use list_company_questionnaires to… - `update_candidate_questionnaire` _(destructive)_ — Submit responses for a candidate questionnaire. Use get_candidate_questionnaires to see pending questionnaires and their question IDs. - `add_candidate_by_resume` _(write)_ — Use this when the user has a resume file and wants to add that person as a candidate for a job. Creates a new candidate by uploading and parsing a resume file.… - `add_candidate_document` _(write)_ — Attach a document file to an existing candidate. The file bytes must be base64-encoded. Per Breezy docs, this is also how you add a resume to an existing… - `list_webhook_endpoints` _(read)_ — List all webhook endpoints configured for a Breezy HR company. - `get_webhook_endpoint` _(read)_ — Get details for a specific webhook endpoint including its URL, events, and status. - `create_webhook_endpoint` _(write)_ — Create a new webhook endpoint for a Breezy HR company. Webhooks notify your URL when events occur (e.g. candidate stage changes). - `update_webhook_endpoint` _(destructive)_ — Update an existing webhook endpoint. Can change URL, events, description, or enabled status. - `delete_webhook_endpoint` _(destructive)_ — Permanently delete a webhook endpoint. This cannot be undone. - `pause_webhook_endpoint` _(write)_ — Pause a webhook endpoint. The endpoint will stop receiving events until resumed. - `resume_webhook_endpoint` _(write)_ — Resume a paused webhook endpoint. The endpoint will start receiving events again. --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)