Prelim

Created By
Prelim12 days ago
Read AI preliminary phone screens — your roles, candidate scores, transcripts, and analytics.
Overview

Prelim MCP Server

Prelim runs AI-driven preliminary phone screens for high-volume hiring. This MCP server gives any AI assistant (Claude, ChatGPT, Cursor, etc.) read access to your Prelim account's jobs, candidate screens, full transcripts, and analytics.

Tools

  • list_jobs — list open hiring roles in your Prelim org
  • get_job — full details of one role (title, status, screening questions)
  • list_screens — list preliminary screens for a job, with score and disposition
  • get_screen — detailed view of one candidate screen
  • get_transcript — full conversation transcript of a screen
  • get_job_analytics — funnel metrics for a job

Connect

  1. Sign up at prelim.chat
  2. Settings → API Keys → Create
  3. Add to your AI assistant:

Claude.ai / ChatGPT (Developer Mode): Add a custom connector with URL https://mcp.prelim.chat/mcp + Bearer token.

Claude Desktop: edit claude_desktop_config.json:

{
  "mcpServers": {
    "prelim": {
      "url": "https://mcp.prelim.chat/mcp",
      "headers": { "Authorization": "Bearer prelim_..." }
    }
  }
}

Auth is OAuth 2.1 + PKCE for hosted clients or static API key for self-hosted setups.

Server Config

{
  "mcpServers": {
    "prelim": {
      "url": "https://mcp.prelim.chat/mcp",
      "headers": {
        "Authorization": "Bearer prelim_YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
12 days ago
Updated At
12 days ago
Author Name
Prelim
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago