Job Application Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CV_PATH | No | Path to the CV file served by the MCP server. Defaults to the example CV. | |
| GROQ_API_KEY | Yes | Groq API key used by the LLM for tools such as drafting cover letters. Create one at console.groq.com/keys and put it in GROQ_API_KEY. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Search current job vacancies in Germany (Arbeitnow job board). |
| read_cvA | Read the user's CV: profile, languages, skills and citable facts. |
| score_matchA | Score how well one vacancy fits the CV, from 0 to 100. |
| draft_cover_letterA | Write a cover letter draft for one vacancy, using only facts from the CV. |
| request_approvalA | Ask the user to approve an action on a draft. You cannot approve it yourself. |
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 5 tools
Each tool occupies a distinct stage of a linear pipeline: search_jobs (discover vacancies), read_cv (load candidate facts), score_match (evaluate one vacancy), draft_cover_letter (produce a grounded draft), and request_approval (gate an action). Descriptions reinforce the boundaries, e.g. score_match requires a job_id from search_jobs and draft_cover_letter says to score first, so an agent cannot easily pick the wrong one.
All five names are snake_case verb_noun pairs (search_jobs, read_cv, score_match, draft_cover_letter, request_approval). The verb accurately reflects each tool's action, and there is no mixing of conventions or casing styles.
Five tools map exactly to the five steps of the stated purpose (find job, read CV, score, draft, approve), with no redundant or speculative extras. This is a well-scoped, minimal surface for a single-agent workflow.
The end-to-end lifecycle (search → CV → score → draft → approval/export) is fully covered, including a deliberate safety boundary on sending. Minor gaps remain: there is no way to list or retrieve previously saved drafts, and no way to revise a draft (each call creates a new one), so agents must work around those limits.