Gem

Query recruiting analytics, candidate profiles and interview feedback.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Gem connector does

The Gem MCP server — Gem calls it GeMCP — connects a Gem recruiting workspace to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 25 tools that search candidates, jobs and applications, query hiring analytics, and write notes, projects and dashboards. Sign-in is OAuth, scoped to your own Gem permissions.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Gem tools (25)

  • add_note_to_person
  • archive_project
  • delete_widget
  • edit_project_enrollment
  • get_application
  • get_dashboard
  • get_job
  • get_metrics_catalog
  • get_opening
  • get_person
  • get_project
  • get_saved_report
  • get_tasks
  • get_widget
  • query_metrics
  • save_dashboard
  • save_project
  • save_widget
  • search
  • search_applications
  • search_jobs
  • search_people
  • search_users
  • submit_mcp_feedback
  • whoami

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The OAuth scopes are identity claims and nothing else. Gem's authorization server and the server's own RFC 9728 descriptor both advertise exactly openid, email and profile. None names an object or a verb, so the consent screen cannot separate reading a candidate profile from deleting a dashboard widget. Your Gem user permissions are the only boundary, and they were designed for a person in a UI, not for an agent acting at machine speed.
  • Gem publishes no tool list, and says the list moves. The 25 names come from Anthropic's directory. Gem's FAQ directs users to ask their assistant what tools are available, which makes the surface a runtime question rather than a documented one. We could not diff against a vendor enumeration because none exists.
  • The server's own documentation link is login-walled. Gem's RFC 9728 descriptor advertises resource_documentation at https://www.gem.com/api-docs/mcp. That URL redirected to a Gem login page on 2026-08-23, so the machine-readable pointer to the connector's reference documentation resolves to nothing for anyone without a Gem account. We did not attempt to bypass it. The public help-centre articles cited below are the usable documentation.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here — including for edit_project_enrollment, the one name where parameters would settle a real question.
  • edit_project_enrollment is undocumented. Gem describes no such tool. We found no path from it to a sent message and two documented reasons to think there is none, but we could not confirm it either way. Do not include it in a blanket approval.
  • Gem's AI safeguards do not extend to MCP. PII redaction, bias warnings and the BABL bias audit govern Gem's in-product AI features. Candidate records retrieved through GeMCP reach your assistant unredacted, and Gem's AI compliance article does not mention MCP.
  • Whether MCP-assisted screening is an AEDT is unresolved. Gem argues its own tools fall outside NY Local Law 144 because they support rather than make decisions. That argument is about Gem's features, not about a general-purpose model you have pointed at candidate data. Take it to counsel rather than inheriting Gem's position.
  • Analytics answers depend on products you may not own. Gem states that dashboard, Talent Compass, sourcing and outreach questions may require specific products to be enabled, so a metric question can fail for entitlement reasons that look like a broken connector.
  • We found no published rate limits for GeMCP. Gem documents slow responses on broad cross-object questions and recommends narrowing to one role, project or period, but names no numeric limit.
  • No prompts or resources could be checked. The 401 meant we never read the server's initialize capabilities, so we cannot say whether it serves prompts or resources. Anthropic's directory lists no prompt names, which is not evidence either way.

Frequently asked questions

Can the Gem connector send outreach to a candidate?

No tool among the 25 sends a message or enrolls anyone in a Sequence. Gem's outreach product is absent from the listing entirely — no tool name contains send, message, sequence, email or campaign. Gem's help centre documents that Sequences send automatically on a schedule once started, so the absence is the safety property here, and it is worth re-checking because Gem says the tool list changes.

Does edit_project_enrollment start an outreach sequence?

Gem does not document what that tool does, so treat it as unresolved. A Gem Project can carry a default Sequence, and Gem states that adding someone to such a Project creates a draft rather than sending. But Gem also states that mechanism works only through the Gem Chrome extension, which an MCP server is not. We could not confirm the behaviour either way.

What candidate personal data can the Gem MCP server read?

Names, profiles, applications and interview feedback about identified people. Gem's own prompt guide suggests asking the assistant to pull interview feedback across all rounds and to surface where reviewers disagree. get_person, get_application and search_people reach candidate records directly, which makes this regulated employment data under GDPR and EEOC recordkeeping rules.

Do Gem's AI bias safeguards apply to the MCP connector?

No. Gem documents PII redaction, bias warnings and a BABL third-party bias audit for its in-product AI features such as AI Sourcing and AI-powered Application Review. Those controls govern Gem's own Azure OpenAI pipeline. GeMCP hands raw candidate records to whichever assistant you connected, so none of those safeguards travel with the data.

What OAuth permissions does the Gem MCP server request?

Only identity claims. Gem's authorization server advertised openid, email and profile on 2026-08-23, and the server's RFC 9728 descriptor lists the same three. None of them names a read or a write, so consent cannot separate reading a candidate profile from deleting a dashboard widget. Gem's own user permissions are the only boundary.

Which Gem MCP tools change or delete data?

Eight of the 25: add_note_to_person, archive_project, delete_widget, edit_project_enrollment, save_dashboard, save_project, save_widget and submit_mcp_feedback. Only delete_widget carries an obvious destructive verb, so a scan for delete or remove finds one of the eight and misses the seven save, add, edit and archive writes.

Can an admin turn off Gem MCP access for their team?

Yes, at the team level. Gem's setup article states that admins can navigate to Team Settings and toggle MCP access on or off for their users. Individual access is further bound by each user's existing Gem permissions, and Claude Team or Enterprise workspaces may additionally require an Owner to add the connector before members can connect.

Does Gem publish a list of its MCP tools?

No. Gem's FAQ states that available tools are subject to change and tells users to ask their AI assistant what tools are available. The 25 names on this page come from Anthropic's directory, not from Gem. That makes the list unverifiable against any vendor enumeration and explicitly a moving target.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Gem to work.

Connect Gem once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.