Temporary MCP setup

Connect recruiter agents to Loom Ledger

Loom Ledger exposes a remote MCP server for recruiter workflows. Use the temporary Vercel host below until a permanent domain is available.

MCP server URLhttps://loom-ledger-web.vercel.app/mcp/recruiter
Protected resource metadatahttps://loom-ledger-web.vercel.app/.well-known/oauth-protected-resource
OAuth authorization metadatahttps://loom-ledger-web.vercel.app/.well-known/oauth-authorization-server
Authorize endpointhttps://loom-ledger-web.vercel.app/oauth/authorize
Token endpointhttps://loom-ledger-web.vercel.app/oauth/token
Current status

Limited Phase 6 setup

Temporary host

This endpoint is not listed in public registries yet. Agents must be configured manually and may need the recruiter to sign in to Loom Ledger before tools are available.

Loom Ledger now acts as the MCP OAuth authorization server. Clerk remains the human sign-in layer, so recruiters can authenticate with email, magic link, Google, or any other Clerk method enabled for the app. The agent receives a Loom Ledger scoped bearer token, not a Clerk browser session.

Read tools

candidate_search, candidate_match_detail, compensation_fit, and taxonomy_lens_info.

Lenses: Loom, SOC, WEF, NACE, O*NET, CIP, and occupation profiles.

Write tools

shortlist_candidate, remove_from_shortlist, request_candidate_intro, and create_recruiter_note. Write actions require explicit confirmation.

Candidate control

Search respects recruiter visibility, candidate recruiting opt-in, compensation visibility, and contact policy.

ChatGPT

Custom app or API MCP tool

Remote only
  1. Open ChatGPT workspace app settings. An admin or owner may need to enable custom apps or developer mode.
  2. Create a custom MCP-backed app and use the MCP server URL above.
  3. Connect the app, complete the Loom Ledger sign-in and authorization flow, then invoke it from the tools or apps menu.
  4. For write actions, review ChatGPT's confirmation prompt and the Loom Ledger confirmation preview before approving.

API developers can also pass the server as an MCP tool in the Responses API:

{
  "type": "mcp",
  "server_label": "loom_ledger_recruiter",
  "server_description": "Search opted-in Loom Ledger candidates and manage recruiter workflows.",
  "server_url": "https://loom-ledger-web.vercel.app/mcp/recruiter",
  "require_approval": "always"
}
Open ChatGPT app docs
Claude

Custom connector

Remote MCP
  1. In Claude, open Customize or Settings, then Connectors.
  2. Choose Add custom connector and enter the MCP server URL.
  3. For Team or Enterprise plans, an owner may need to add the connector before members can connect it.
  4. Click Connect, authenticate and authorize with Loom Ledger, then ask Claude to use the Loom Ledger recruiter connector.

Claude connects to remote MCP servers from Anthropic's cloud infrastructure, so the temporary host must remain publicly reachable.

Open Claude connector docs
Gemini

Gemini CLI MCP config

CLI
  1. Open the Gemini CLI settings file used by your workspace.
  2. Add a mcpServers entry using Streamable HTTP.
  3. Restart Gemini CLI and run its MCP listing command to confirm the Loom Ledger tools are discovered.
{
  "mcpServers": {
    "loomLedgerRecruiter": {
      "httpUrl": "https://loom-ledger-web.vercel.app/mcp/recruiter",
      "authProviderType": "dynamic_discovery",
      "trust": false
    }
  }
}
Open Gemini CLI MCP docs
Grok

Custom MCP connector

Remote MCP
  1. Go to grok.com/connectors.
  2. Click New Connector, choose Custom, and enter the MCP server URL.
  3. Complete the Loom Ledger authentication and authorization flow if prompted.
  4. Ask Grok to use the Loom Ledger recruiter connector for candidate search or recruiter workflow tasks.

xAI API developers can configure a remote MCP tool with:

{
  "type": "mcp",
  "server_url": "https://loom-ledger-web.vercel.app/mcp/recruiter"
}
Open Grok connector docs
Suggested first prompt

Smoke test after connecting

Use Loom Ledger to list the available recruiter tools, then search for opted-in candidates for a junior software engineer role focused on API integrations, GitHub code review, and stakeholder demos. Do not run write actions unless I approve the confirmation preview.

When the permanent domain is ready, replace the temporary host everywhere and publish the registry metadata from that verified domain.

Open recruiter matcherBack to home