Skip to main content
Glama
CaseyTTS

Bullhorn MCP Agent

by CaseyTTS

Related Servers

Alternatives to Bullhorn MCP Agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to manage JobZyn jobs and candidates through MCP tools for creating, updating, unpublishing jobs, retrieving candidate applications, and linking external IDs.
      5
      38 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A hosted, OAuth-authenticated MCP endpoint exposing 176 tools that let AI assistants read and write jobs, candidates, applications, interviews, scorecards, prospects, talent pools, and imports within an organization's own applicant tracking data, scoped to the signed-in user's existing permissions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI assistants to securely access a user's job-search account, letting them search and save jobs, analyze job fit, and retrieve job queue and profile summaries with links back to the web app.
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to query Bullhorn CRM data using natural language through direct REST API access with OAuth 2.0 authentication.
      6
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search jobs, retrieve job details, and view or update career-profile data such as experiences, job summaries, career goals, and technical skills through MCP tools.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible agents to search live job postings, score resumes against specific postings, and create or update tracked applications through their pipeline.
      4
      MIT

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation3/5

    There is substantial overlap between the generic search tools (search_entities Lucene, query_entities SQL-like, find_records structured filters) and the specific ones (list_jobs, list_candidates, get_recent_placements), so an agent can easily pick the wrong path to the same data. get_notes versus get_activity (which includes note_created) and connection_status versus setup_status versus bullhorn_session also blur together. The very detailed descriptions do help differentiate them, keeping this from being worse than a 3.

    Naming Consistency3/5

    Most tools follow a verb_noun snake_case pattern (list_jobs, get_candidate, propose_mapping_changes, confirm_write), which is readable and predictable. However several tools break the pattern with noun or non-standard verb forms (connection_status, setup_status, bullhorn_session, manage_mapping_profile). The mix is understandable but not fully consistent.

    Tool Count3/5

    23 tools is on the heavy side and sits in the borderline range where redundancy costs appear. The breadth (CRM reads, mapping-profile governance, safe-write pipeline, activity and metrics) justifies many tools, but the generic search trio overlaps with the resource-specific list tools, suggesting some could be consolidated.

    Completeness3/5

    The server has strong read coverage (jobs, candidates, placements, notes, activity, metrics) and a well-governed write path, but it lacks create/update for the core CRM entities (no candidate/job/submission/placement creation). For a Bullhorn agent the only real writes are notes and resume upload, a notable lifecycle gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues