JobSpy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENABLE_SSE | No | Enable Server-Sent Events transport | 0 |
| JOBSPY_HOST | No | Host for HTTP server | 0.0.0.0 |
| JOBSPY_PORT | No | Port for the MCP server | 9423 |
| JOBSPY_ACCESS_TOKEN | No | Access token for JobSpy API (if required) | |
| JOBSPY_DOCKER_IMAGE | No | Docker image to use for JobSpy | jobspy |
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsC | Search for jobs across various job listing websites |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_jobs | Extract job search parameters from a natural language query |
| job_recommendations | Get personalized job recommendations based on skills and preferences |
| resume_feedback | Get professional feedback on your resume for specific roles and industries |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so an agent cannot confuse it with another tool. The name and description clearly indicate a single, dedicated job search action.
The sole tool uses a clear snake_case verb_noun format (search_jobs) that matches common MCP conventions. With only one tool there is no full pattern to assess, but no inconsistency is present.
A single tool covering job search across multiple sites is functional, but the server feels minimal and offers no supporting operations. It sits at the borderline of being too few tools for a general job-search domain.
The tool covers centralized searching across job listing websites, which satisfies the basic stated purpose. However, there are no tools for inspecting individual job details, refining saved searches, or acting on results, leaving notable gaps for a wider job-search workflow.