JobPilot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_KEY | Yes | Your Notion internal integration token (starts with secret_) | |
| NOTION_DATABASE_ID | No | The ID of the Notion Job List database (can be left blank initially) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_notion_dbA | One-time setup: creates the Job List DB in Notion with the correct schema. If NOTION_DATABASE_ID is already set and valid, it skips creation. Run this before using log_to_notion. |
| parse_cvA | Parse a CV/resume (PDF path or raw text) and extract a structured candidate profile: name, skills, years of experience, job titles, education, and a short bio summary. |
| search_jobsA | Search for open job listings on RemoteOK, We Work Remotely, and Himalayas based on a role keyword and optional filters. |
| score_job_fitA | Score how well a candidate profile matches a job listing (0–100). Returns a fit score, matched skills, missing skills, and a recommendation. |
| generate_cover_letterB | Generate a tailored, professional cover letter for a specific job based on the candidate profile. |
| generate_follow_upB | Generate a professional follow-up email for an application that has not received a response. |
| log_to_notionC | Log a job application to the Notion Job Tracker database with full details. |
| update_application_statusB | Update the status of an existing job application in Notion (e.g. from Applied → Interview). |
| auto_applyA | Automatically search, score, generate cover letters, and apply to N remote jobs matching the candidate profile. Uses browser automation (Playwright) to fill and submit application forms. Logs all applications to Notion. |
| linkedin_applyA | Search LinkedIn for jobs and auto-apply using Easy Apply. Uses a persistent browser session — on first run the user logs in manually; all subsequent runs reuse the saved session. Each application result includes a 'confirmed' flag, confidence level, confirmation message, and a screenshot path so you can verify every submission. |
| indeed_applyA | Search Indeed for jobs and auto-apply using Indeed's native 'Easily Apply' flow. Uses a persistent browser session — on first run the user logs in manually; all subsequent runs reuse the saved session. Each application result includes a 'confirmed' flag, confidence level, confirmation message, and a screenshot path so you can verify every submission. |
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 11 tools
Tools have distinct purposes overall, but auto_apply, indeed_apply, and linkedin_apply have overlapping functionality. Descriptions help differentiate, but an agent might still be confused about which apply tool to use.
Tool names follow a mostly consistent snake_case pattern with imperative verbs. Minor deviations like 'indeed_apply' vs 'auto_apply' exist, but overall pattern is readable and predictable.
11 tools is well-scoped for a job application automation server. Each tool serves a necessary function without unnecessary redundancy.
The tool set covers the main job application workflow, but missing a tool to list or retrieve existing applications from Notion. This is a minor gap that agents could work around.