Bullhorn MCP: what exists and what Bullhorn allows
The short answer
Bullhorn has no official MCP server. Bullhorn’s API Fair Use Policy, dated 17 December 2025, says you must not move data in or out of Bullhorn with unauthorized solutions such as MCPs, or use the API to connect third-party AI or LLM tools, without Bullhorn’s explicit written permission. Bullhorn’s own AI, including Amplify Chat, works inside Bullhorn rather than through Claude or ChatGPT. Community and commercial MCP servers for Bullhorn exist, but Bullhorn doesn’t endorse them. Agencies that want an assistant to work with screened candidates can connect it to a tool with its own MCP server, such as Beatview, and keep Bullhorn as the system of record.
Every Bullhorn detail comes from Bullhorn’s own documentation, read on 1 October 2026. Beatview is not affiliated with Bullhorn.
Bullhorn and AI assistants at a glance
| What the documentation says | |
|---|---|
| Official MCP server | None found on Bullhorn’s website, knowledge base, API documentation or AI release notes |
| Policy on MCP | Bullhorn’s API Fair Use Policy bars moving data in or out with unauthorized solutions “like Model Context Protocols” without its explicit written permission |
| Third-party AI tools | The same policy bars using the API to connect third-party AI or LLM tools for viewing or updating data without written permission |
| Connectors and middleware | Bullhorn says it does not permit third-party connector or middleware companies to build integrations |
| Bullhorn’s own AI | Amplify Chat, announced in May 2026, lets users ask about their Bullhorn data in everyday language inside Bullhorn; Bullhorn also offers an AI Assistant |
| API credentials | Not self-service: you request a client ID, secret, API username and password from Bullhorn Support |
| Editions with custom API integrations | Bullhorn’s editions table lists them on Front Office Growth and Front Office Enterprise |
| API limits | Up to 1,500 requests a minute, 100,000 calls a month and 50 active sessions unless agreed otherwise, shared per OAuth client ID |
| Unofficial MCP servers | Community and commercial servers exist. Bullhorn doesn’t endorse them, and they rely on API access its policy restricts |
What agencies on Bullhorn can do instead
Four routes that stay within what Bullhorn documents.
- 01
Step 01
Use Bullhorn’s own AI
Amplify Chat and Bullhorn’s AI Assistant work inside Bullhorn with your Bullhorn data. Check with Bullhorn which of your editions include them. - 02
Step 02
Ask Bullhorn for written permission
If you want an MCP server or an AI assistant to read or update Bullhorn data through the API, Bullhorn’s policy requires its explicit written permission first. - 03
Step 03
Use an approved Marketplace partner
Bullhorn’s Marketplace lists approved partners that integrate with Bullhorn, and Bullhorn says it doesn’t charge integration fees. - 04
Step 04
Give your assistant tools with their own MCP server
Connect your assistant to tools that hold their own data, such as Beatview for screening and AI interviews, and keep Bullhorn as the system of record.
Bullhorn API rules that affect AI tools
Limits to know
- Bullhorn’s API Fair Use Policy requires its explicit written permission before an MCP or third-party AI tool reads or updates Bullhorn data through the API.
- Bullhorn won’t provide an API key that a customer intends to give to a third-party vendor not contracted with Bullhorn.
- API credentials aren’t self-service; they come from Bullhorn Support, one request per environment.
- Default limits: 1,500 requests a minute, 100,000 calls a month and 50 active sessions, shared across everything using the same OAuth client ID.
Before you try an unofficial server
- Check your Bullhorn agreement and the API Fair Use Policy, and get Bullhorn’s written permission.
- Ask what the server stores, where it runs and who can see the candidate data it handles.
- Prefer read-only access, and test in a Bullhorn sandbox before connecting live data.
- Remember that API calls count against your organization’s shared rate limit.
Bullhorn stays your system of record. Beatview brings screening to your assistant.
Beatview’s MCP server connects Claude, ChatGPT, Gemini and Cursor to Beatview itself, not to Bullhorn, so it doesn’t use Bullhorn’s API. Your assistant can open roles, compare applicants by their resume and AI interview scores, brief you before a client call and send interview invitations, while your consultants keep working in Bullhorn.
One address
Add https://platform.beatview.ai/mcp to Claude, ChatGPT, Gemini or Cursor. It is included on every Beatview plan, including Free.
Evidence, not just records
Beatview returns each applicant’s resume match score with reasons and a structured AI interview assessed answer by answer.
You stay in charge
The assistant confirms with you before moving a candidate or sending an interview invitation, and recordings never leave Beatview.
Try with Beatview connected
- “Who are the strongest applicants for the Account Manager role, by interview score?”
- “Brief me on Maya Chen before my client call: strengths, concerns and her weakest answer.”
- “Draft a client update for this role: pipeline numbers and the top three, no contact details.”
Bullhorn MCP: frequently asked questions
Still deciding?
Bring a live vacancy and we’ll walk through where automation ends and recruiter review begins.
Not an official one. As of 1 October 2026, Bullhorn’s website, knowledge base, API documentation and AI release notes describe no Bullhorn MCP server. Bullhorn’s AI, such as Amplify Chat, works inside Bullhorn.
Not through the API without permission. Bullhorn’s API Fair Use Policy says you must not use the API to connect third-party AI or LLM tools for viewing or updating data without its explicit written permission, and it names MCPs among unauthorized solutions. Ask Bullhorn before connecting any assistant.
Community and commercial MCP servers for Bullhorn exist. Bullhorn doesn’t endorse them, and they depend on API access that its policy restricts, so get Bullhorn’s written permission before using one.
Yes. Bullhorn announced Amplify Chat in May 2026, a conversational interface that lets users ask about their Bullhorn data in everyday language, and it offers an AI Assistant. Both run inside Bullhorn.
They aren’t self-service. You request a client ID, client secret, API username and password from Bullhorn Support, one request per environment. Bullhorn’s editions table lists custom API integrations on Front Office Growth and Front Office Enterprise.
Yes. Bullhorn stays your system of record and Beatview handles screening and AI interviews alongside it. Beatview’s own MCP server lets your assistant work with Beatview’s screened candidates on every plan, including Free. To connect Beatview and Bullhorn themselves, use Zapier on Enterprise or ask us about a native integration.
Where these details come from
Bullhorn’s own documentation, read on 1 October 2026. MCP servers change quickly; check the source before you rely on a detail.
- Bullhorn API Fair Use Policy
- Bullhorn API access FAQs
- Bullhorn KB: API usage limits
- Bullhorn KB: platform editions
- Bullhorn KB: requesting REST API credentials
- Bullhorn press release: Amplify Chat at Engage 2026
Beatview publishes this guide and runs its own MCP server, which works alongside Bullhorn. Where Bullhorn does not document something, we say so rather than guess. Spotted a change? Tell us.