Career Agent Workbench MCP Server
Related Servers
Alternatives to Career Agent Workbench MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes the entire job-search workflow as 13 chat-driven tools, letting users refresh a ranked feed of live postings from employers' public hiring APIs, view and score job descriptions, tailor and render truthful one-page LaTeX resumes, review skill gaps and screening answers, and log applications. It keeps a human in the loop, since nothing is ever submitted automatically.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search a shared catalog of projects, roles, orders, participants, and mentors, create and update listings or profiles, draft proposals, and search and apply across external freelance and job platforms while keeping platform credentials local.13-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to serve as a personal career analyst by searching, matching, and explaining job recommendations, managing job applications, and syncing public job boards through standardized MCP tools.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to search, rank, and explain job matches through a secure read-only interface that blocks prompt injections and unsafe content.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP host to search and retrieve job listings from a public jobs board via the search_jobs and get_job tools, returning structured results such as title, company, location, remote status, and apply/source URLs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts and agents to search public job listings and retrieve job details via standardized search_jobs and get_job tools, supporting keyword, location, remote, date, and limit filters. It is read-only and rate-limited, returning normalized results with apply and source URLs.MIT
TDQS
Scored across 4 tools
Search and find_matching both return job listings but serve distinct purposes: ad-hoc searching vs. preconfigured matching. The two get tools are clearly differentiated by normalized vs. raw payload.
All tool names use snake_case with a verb prefix and include 'linkedin_job(s)' as the core noun. Minor variation like 'matching' as a modifier and 'details'/'raw_payload' suffixes does not break the overall pattern.
Four tools is well within the ideal range for a focused job-search server. Each tool serves a clear purpose without redundancy.
The server covers the complete read-only workflow: search to discover jobs, retrieve normalized details, access raw payload for debugging, and run configured matching. No dead ends exist for this domain.