Djinni MCP
Related Servers
Alternatives to Djinni MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables searching job listings, tracking applications, managing resumes, and tailoring resumes to job posts, all locally via MCP.20-
- AlicenseBqualityBmaintenanceEnables MCP clients to search job listings, read complete job descriptions, manage local search presets and candidate pools, and prepare application or message drafts. Optional session-backed chat reading and human-confirmed single-action execution are also supported.23MIT
- AlicenseNot gradedqualityDmaintenanceEnables to interact with job application workflows through MCP, allowing users to find jobs, generate non-trivial applications with proof-maps, and build offline dashboards, all without auto-submitting.Apache 2.0
- 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
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to search job listings and view or update career profile data, including work history, job summaries, career goals, and technical skills.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes job-search and application-management capabilities to compatible AI clients, enabling discovery of vacancies, drafting of tailored application materials, and coordinated human-approved submissions.MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct resource/action: search, read job, workflow docs, profile read/write, history read, exclusion toggle, and saved-search write. The only mild overlap is between get_workflow/get_profile/get_history, all of which are read-at-start tools, but the descriptions clarify when each applies. An agent might briefly hesitate on whether to call get_profile or get_history first, but boundaries are largely clear.
Every tool follows a consistent verb_noun pattern (search_jobs, get_job, get_workflow, get_profile, update_profile, get_history, set_job_excluded, save_search). No mixed casing or verb styles. Read/write intent is also obvious from verb choice (get vs update/set/save).
Eight tools is well-scoped for a job-search assistant: search, inspect, profile, history, exclusions, and saving. No tool seems redundant, and there is no missing obvious chunk that would demand more surface. The count keeps the agent's choice space manageable.
The surface covers discovery (search_jobs), detail (get_job), user context (get_profile/update_profile), memory (get_history), suppression (set_job_excluded), and output (save_search), plus onboarding (get_workflow). A minor gap is that there is no explicit way to clear or list saved searches/history batches beyond reading history, and no batch/exclusion list retrieval. Core workflows are nonetheless complete for the stated purpose.