jobctl
Job application tracker for developers - AI agents write over MCP, you review in a dashboard.
| Endpoint | https://app.jobctl.app/mcp (streamable-http) |
|---|---|
| Registry version | 0.5.1 |
| Now | 11 tools · grade B (84) · pin ts_b3ca7b5e0429383416e9d3afe31df953 · protocol 2025-06-18 |
| First / last listed | 2026-10-28 01:52 UTC / 2026-10-28 01:52 UTC |
| Grade over time | 2026-10-28: B (84), 11 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: add_application list_applications update_application add_note log_interview get_due get_planned attach_analysis attach_file attach_interview_file get_application
add_application | Track a new job application. Pass either a single `raw` line — `add_application({raw: "Bosch, Tech Lead, prio A, due friday, remote, via LinkedIn"})` — or structured fields (`company` and `role` required then). Returns the created application and possible-duplicate warnings; if duplicates are listed, tell the user instead of creating again. params: raw, company, role, status, priority, remote, remote_note, source, url, location, salary_asked, salary_range_min, salary_range, cv_variant, match_notes, next_interview_at, next_action, next_action_due, applied_at |
list_applications | List job applications. Filter by view (active = default working set, archive = rejected/withdrawn/no-response), status list, priority, or free-text search in company/role. Example: `list_applications({view: "active"})`, `list_applications({q: "bosch"})`. params: view, status, priority, q, limit |
update_application | Update fields of an application (get the id from list_applications). Status changes are logged to the timeline automatically. Example: `update_application({id: "…", status: "interview", next_action: "prepare system design", next_action_due: "2026-07-20"})`. params: id*, company, role, status, priority, remote, remote_note, source, url, location, salary_asked, salary_range_min, salary_range, cv_variant, match_notes, next_interview_at, next_action, next_action_due, applied_at |
add_note | Append a free-text note to an application timeline — recruiter call summaries, interview instructions, pasted messages. Multiline markdown is fine. Example: `add_note({application_id: "…", text: "Recruiter: team of 5, on-call rotation, offer range 85-95k"})`. params: application_id*, text* |
log_interview | Log an interview for an application (max 10 per application): when it takes place, its status (planned or done), who attends (each with an optional profile link), related links (prep materials the company sent, meeting URL), and a short recap of what was discussed. Also keeps the application's next-interview date in sync. Example: `log_interview({application_id: "…", scheduled_at: "2026-07-20T14:0 params: application_id*, scheduled_at*, status, attendees, links, recap |
get_due | What is burning today: applications with next_action_due today or overdue. Call this when the user asks "what should I do today?" about their job search. params: none |
get_planned | What is actually SCHEDULED: interviews with their time, attendees and meeting links, plus the actions falling due, for today, tomorrow, or the next seven days. Use this whenever the user asks what is planned, what the day or week looks like, or before proposing a time to anyone — get_due only knows action deadlines and is blind to booked interviews. Example: `get_planned({range: "tomorrow"})`. params: range |
attach_analysis | Attach a markdown company analysis (research you produced) to an application. Single document per application — a new call REPLACES the previous one. Max 100000 bytes (~100 KB) of utf-8. The user reads it in the dashboard, e.g. before an interview. Example: `attach_analysis({application_id: "…", markdown: "# Bosch\n\n## Culture…"})`. params: application_id*, markdown* |
attach_file | Attach or replace a file on an application so the user sees it in the dashboard: a CV/resume (kind: 'cv') or a cover letter (kind: 'cover_letter'). Pass the file bytes as base64 in data_base64. One file per (application, kind) - a new call REPLACES the previous one. Max ~5 MB; pdf/doc/docx/txt/md (MIME is inferred from the filename if you omit it). Call this whenever you generate a tailored CV or params: application_id*, kind*, filename*, data_base64*, mime |
attach_interview_file | Attach prep material to a specific interview so the user sees it next to that round in the dashboard: the prep document you wrote, the job description, a deck, notes the company sent. Max 3 files per interview, 20000000 bytes (20 MB) each; pass the bytes as base64. Get interview ids from get_application. Example: `attach_interview_file({application_id: "…", interview_id: "…", filename: "prep-round params: application_id*, interview_id*, filename*, data_base64*, mime |
get_application | Full detail of one application: all fields, contacts, recent timeline events, and whether a company analysis is attached (fetch it via the dashboard or attach_analysis to replace). params: id* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.