mcp-lightcast
Related Servers
Alternatives to mcp-lightcast
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying U.S. Dept. of Labor CareerOneStop data for occupations, salaries, and salary comparisons across locations.94 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to search and retrieve job listings, and to read or manage career profile data such as work history, job summaries, career goals, and technical skills.-
- AlicenseNot gradedqualityBmaintenanceEnables querying the O*NET occupation taxonomy, including keyword search, occupation details, skills, and associated tools and technology.96 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to search and retrieve job postings and to view, create, update, or delete career-profile information such as work experiences, summaries, goals, and technical skills.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI/ML job-market analysis by exposing tools and resources to search and inspect postings, rank skill demand, compute skill gaps, manage a shortlist, and retrieve market statistics, plus a reusable career-advisor prompt.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search job listings and retrieve or update a user's career profile, including work experiences, job summaries, career goals, and technical skills through natural language.-
TDQS
Scored across 37 tools
Most tools map cleanly to a distinct resource and action (skills, titles, postings, LMI, similarity, pathways), and descriptions explicitly clarify subtle boundaries such as related vs. similar skills. The main ambiguity is among the three composite pipeline tools (normalize_title_and_get_skills, normalize_title_and_extract_skills, analyze_job_posting_skills), which overlap in workflow and could still be misselected.
Tool names consistently use snake_case with a predictable verb_noun pattern (search_skills, get_skill_details, query_core_lmi, map_taxonomy_concepts). Longer composite names remain readable and follow the same convention.
The 37 tools span roughly eight distinct Lightcast sub-APIs (Skills, Titles, Postings, Classification, Similarity, Core LMI, Benchmarks, Pathways), so many tools are justified. However, the count is heavy, and the redundant composite workflow tools push it beyond a comfortably scoped surface.
The surface covers discovery/metadata, search, detail retrieval, bulk retrieval, mapping, classification, benchmarking, and cross-API composites for every major taxonomy and dataset. Since the APIs are read-only analytics services, there are no obvious missing create/update/delete lifecycle operations.