tracker-mcp
Related Servers
Alternatives to tracker-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables tracking job applications through a pipeline, scheduling follow-ups, and summarizing job search progress via natural language.7-
- AlicenseAqualityBmaintenanceEnables managing a job search through natural language: tracking applications, discovery leads, interview prep, and resume generation. Connects to Claude via MCP to read and update local Excel files and documents.35ISC
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage a personal job application tracker, allowing users to list, add, update, and delete job applications with company, role, and status details through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage job applications and companies in a local SQLite-backed tracker, including searching, creating, updating, and deleting postings and companies, plus reading and updating shared job-search context.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to read and update the local job-search tracker, adding postings from screenshots, pasted text or links, drafting application emails, syncing Gmail to log sent applications and replies, and answering questions about what's due or which jobs match a criteria. Every change is validated and appears live on the dashboard with a timeline entry.MIT
- FlicenseNot gradedqualityDmaintenanceManages job applications, companies, roles, statuses, deadlines, and reminders through natural language queries.-
TDQS
Scored across 25 tools
Despite 25 tools, boundaries are sharply drawn: single vs batch pairs (add_application/add_applications, set_status/set_statuses) are explicit, and the write tools deliberately cross-reference each other (set_status vs edit_application vs log_followup vs reschedule_followup vs mark_applied). Analytics tools are separated by metric (summary=counts, funnel=conversion, reply_times=latency), and the read/write pairs (stale_applications/close_stale, check_tracker/fix_tracker, followups_due/calendar_events) are clearly labelled as such.
Consistent snake_case throughout with a predictable verb_noun pattern for actions (add_application, set_status, edit_application, log_followup, fix_tracker, undo_last_write). The deviation is a handful of noun-only query names (summary, funnel, reply_times, followups_due, stale_applications, calendar_events), which are readable but break the pattern rather than fitting the verb_noun convention.
At 25 tools this sits at the heavy end for a personal job-application tracker. Each tool has a real job, but the surface is inflated by four single/batch write pairs, four overlapping analytics queries, and two near-identical calendar export paths, several of which could be folded into one tool with a batch argument.
Coverage is unusually thorough: CRUD, batch writes, undo, audit log, diagnostics and repair, analytics, schema extension (add_column), and calendar export. The notable gap is row deletion — there is no remove_application tool, so stale or erroneous entries can only be closed or edited, not removed.