jobkit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBKIT_WORKSPACE | Yes | Path to the workspace directory containing resume.tex and application data. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileC | Return the professional profile by reading resume.tex from the workspace root. |
| list_applicationsA | List all job application directories with their files. Each application directory may contain resume.tex, coverletter.txt, META.md, job_posting.md, and any other research or strategy documents. |
| get_applicationC | Get all text file content for one application. Args: company: Company name (e.g. "stripe", "Anthropic") |
| read_application_fileB | Read a single file from an application directory. Args: company: Company name filename: Name of the file to read (e.g. "resume.tex", "META.md", "job_posting.md") |
| save_application_fileB | Save or update a file in an application directory. Args: company: Company name filename: Name of the file to save (e.g. "notes.md", "company_research.md") content: Content to save |
| delete_applicationC | Remove an entire application directory and all its files. Args: company: Company name |
| fetch_urlB | Fetch a URL and return its text content (HTML tags stripped). Args: url: Full URL to fetch |
| save_job_postingB | Fetch a job posting URL or accept pasted text, and save it for a company. Args: company: Company name url: URL of the job posting to fetch (provide url or content, not both) content: Pasted job posting text (provide url or content, not both) |
| compile_resumeA | Compile resume.tex using lualatex. Compiles in a company directory, or the workspace root if no company is specified. Args: company: Company name (optional — omit to compile the base resume) |
| mock_interviewA | Start a mock interview session. Returns a briefing with all application materials, your profile, and interviewer guidance so Claude can play the interviewer role. After the session, save feedback and areas to improve using save_application_file. Args: company: Company name interview_type: One of: behavioral, technical, culture, manager |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Tools have distinct purposes, but fetch_url and save_job_posting both involve fetching URLs; descriptions clarify difference (generic vs. job posting and save).
All tool names follow verb_noun pattern in snake_case, e.g., compile_resume, delete_application, get_profile, mock_interview.
10 tools provide a well-scoped set for job application management without being too few or too many.
Covers CRUD for applications, resume compilation, job posting saving, and mock interviews, but missing an explicit create_application tool to initialize a directory.