Official MCP server for HireSquire. Automate resume screening, candidate ranking, and interview scheduling for autonomous agents.
Scored across 25 tools
Tools target distinct resources and actions within clearly separated sub-domains (screening, billing, scheduling, email), and descriptions draw sharp lines (e.g. purchase_credits charges a saved card vs create_checkout_session generates a Stripe URL; generate_email is single vs bulk_generate_emails is batch). A few pairs (generate_meeting_link vs create_interview, purchase_credits vs create_checkout_session vs list_credit_packs) require reading descriptions to disambiguate, but boundaries are documented.
Nearly every tool follows a clean verb_noun snake_case pattern (create_screening, get_screening_status, list_credit_packs, cancel_screening_job, enable_auto_reload). The only outlier is whoami, which is a widely recognized convention and does not disrupt readability.
25 tools sits at the heavy end of the acceptable range. While the platform spans several genuine sub-systems, some tools are niche or narrow (test_webhook, get_api_schema, generate_meeting_link), pushing the surface toward the borderline-heavy category.
Coverage is broad: full screening lifecycle (create, status, results, cancel, audit, compare, cost estimate), complete billing (balance, transactions, packs, purchase, checkout, auto-reload toggle), and scheduling/email flows plus outcome reporting. Minor gaps exist, such as rescheduling or cancelling an interview and disconnecting a calendar provider, but agents can work around these.
Generate an automated Bias & Disparate Impact Audit for a screening job, aligned with NYC Local Law 144 AEDT and EEOC 4/5ths Rule standards. Evaluates scoring stability against demographic proxy perturbations and computes adverse impact ratios. Produces an unguessable public verification certificate URL.
Inputs: job_id (required), selection_threshold.
Generate multiple personalized candidate emails in a single call. Use this for high-volume outreach batches (max 50 candidates) after a large screening job.
Inputs: type (required), job_id (required), candidate_ids (required), tone.
Immediately stop a running screening job. Use this if the user made a mistake or the job is no longer needed. Note: Credits for already-processed candidates are not refunded.
Inputs: job_id (required).
Perform a side-by-side AI comparison of 2-10 candidates. Use this when you need a clear "Delta Analysis" to decide between top-tier applicants for a final interview.
Inputs: job_id (required), candidate_ids (required).
Securely connect a scheduling provider to HireSquire using an API key. Use this during initial user onboarding or when adding a new interview tool.
Inputs: api_key (required), provider (required).
Generate a Stripe Checkout URL for manual credit purchase. Use this to provide the human user with a secure payment link in the chat.
Inputs: pack, amount.
Confirm an interview time, create a calendar event, and notify the candidate. Use this as the final step in the scheduling process once a time is selected.
Inputs: job_id (required), candidate_id (required), scheduled_at (required), provider, +1 more.
Submit candidate resumes for AI screening against a specific job description. Use this as the entry point for candidate evaluation. It parses resumes, scores them (1-100), and provides reasoning. Side effect: Debits credits from the user account based on the number of resumes.
Inputs: title (required), resumes (required), description (required), webhook_url, +1 more. Returns: job_id, status, message
Turn off automatic credit reloading. Use this to revert to manual credit management.
Inputs: no named parameters.
Set up automatic credit purchases when the account balance drops below a specific threshold. Use this to ensure autonomous agents never run out of credits.
Inputs: amount (required), threshold (required), payment_method_id (required).
Calculate the exact credit cost for a planned screening job based on candidate count. Use this as a pre-flight check before calling "create_screening".
Inputs: candidate_count (required).
Generate a personalized outreach or follow-up email for a specific candidate. Use this after identifying a strong candidate from "get_results" to move them through the pipeline.
Inputs: type (required), job_id (required), candidate_id (required), tone, +1 more. Returns: body, subject
Create a one-off virtual meeting link (Zoom, Google Meet, etc.) via a connected provider. Use this when a standalone meeting URL is needed without a full interview event.
Inputs: topic (required), provider (required), duration.
Fetch the complete OpenAPI 3.0 specification for the HireSquire ecosystem. Use this when you need detailed documentation on REST endpoints or data models.
Inputs: no named parameters.
Query a connected calendar for open interview windows on a specific date. Use this to present valid time options to a candidate before scheduling.
Inputs: date (required), provider (required), duration.
Check the current credit balance and spending metrics for the account. Use this before starting large jobs to prevent "Insufficient Credits" errors.
Inputs: no named parameters.
Fetch a history of credit purchases, spends, and adjustments. Use this for auditing or when a user asks about their recent billing history.
Inputs: limit.
Retrieve detailed candidate scores, AI reasoning, and interview questions for a completed job. Only call this once "get_screening_status" returns a "completed" status.
Inputs: job_id (required), min_score, only_top_n. Returns: has_more, candidates, total_candidates
Check the processing status and progress of a screening job. Use this to poll for completion after calling "create_screening" if a webhook was not provided.
Inputs: job_id (required). Returns: status, progress
List all connected interview scheduling tools (Calendly, Cal.com). Use this to check if a provider is ready before attempting to fetch slots or schedule.
Inputs: no named parameters.
Browse available credit bundles and their current pricing. Use this to help the user choose the best pack for their "purchase_credits" call.
Inputs: no named parameters.
Instantly buy credits using a pre-saved Stripe payment method. CAUTION: This will charge the user's card immediately. Use only when balance is critical.
Inputs: payment_method_id (required), pack, amount.
Submit the final hiring decision (hired/rejected/withdrawn) for a candidate. Use this to close the loop and help refine the specialized AI models for future accuracy.
Inputs: job_id (required), outcome (required), candidate_id (required).
Verify that a webhook endpoint is properly reachable and responds correctly. Use this during setup to ensure the user's server is ready for async notifications.
Inputs: url (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
