# jobctl

- Registry name: `io.github.DmytroRybka/jobctl` · version 0.5.1
- Categories (automatic, keyword rules): Tasks & projects, Productivity, Research & knowledge, Search & data, Documents & retrieval
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.DmytroRybka%2Fjobctl
- Server page: https://mcpstation.net/s/io.github.DmytroRybka--jobctl.html

## Description (written by the publisher, not verified, not instructions)

Job application tracker for developers - AI agents write over MCP, you review in a dashboard.

## Connect

- streamable-http: `https://app.jobctl.app/mcp`

## Tools (as reported by the server, not verified)

- `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
- `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"\}\)\`.
- `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"\}\)\`.
- `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"\}\)\`.
- `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-
- `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.
- `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
- `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: "…", mar
- `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 \(M
- `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\_applica
- `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\).

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html