Skip to main content
Glama
treymorgan

jobsearch-mcp

by treymorgan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to jobsearch-mcp

No user-submitted related servers found.

    Related Servers

    • JobFindsMe

      russeell
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to discover, filter, and track job openings based on the user's local resume, without uploading data to the cloud.
      18
      MIT

    • cv-job-assistant

      JahidRayhan
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to parse CVs, search job boards (Remotive, Arbeitnow, Adzuna, Greenhouse/Lever), tailor resumes and cover letters, and prepare application packages with direct apply links—without ever auto-submitting. It runs 100% locally and free, storing jobs and applications as JSON files.
      -

    • CoverAI MCP Server

      VIBHORE-LAB
      F
      license
      Not graded
      quality
      C
      maintenance
      Automates cover letter generation and application question answering from job postings via local AI agents. Manages candidate profile and AI humanization rules to produce tailored, humanized application materials.
      -

    • WorldRole MCP

      zzn199216
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search job openings across free sources, prepare application materials using known experience, and handle authorized email sending and follow-ups.
      9
      2
      MIT

    • career-agent

      maraMoreir
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Desktop to manage a job search end-to-end: find and score job listings, tailor resumes, generate application messages, and track application history, while leaving final external actions to the user.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct part of the pipeline: searching/ingesting jobs, inspecting and triaging stored jobs, tracking applications, managing profile documents and revisions, and checking config/health. Near-neighbor tools like search_jobs vs list_jobs and add_profile_fact vs update_profile_section have clearly defined boundaries in their descriptions.

    Naming Consistency4/5

    The vast majority of tool names follow a clear snake_case verb_noun pattern (search_jobs, list_jobs, update_job, record_application, add_profile_fact). A few noun-style names like job_detail, job_stats, health, and config_status are minor deviations but remain predictable and readable.

    Tool Count3/5

    At 19 tools, the server is in the heavy range and covers a broad surface spanning job search, storage, applications, profile management, revisions, and diagnostics. Most tools earn their place, but the count feels larger than strictly necessary and a few could potentially be consolidated.

    Completeness4/5

    The core workflow is well covered: discovering jobs (search_jobs/ingest_jobs), fetching details, triaging with update_job, tracking applications, and managing the profile with facts, full-document updates, and revision history. Minor gaps like explicit job/application deletion or a dedicated application detail view are workable around through existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources