jobzyn-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP listen address; use 0.0.0.0 in containers. | 127.0.0.1 |
| PORT | No | HTTP listen port, 1–65535. | 3000 |
| MCP_TRANSPORT | No | Transport to use: 'stdio' or 'http'. Overridden by --transport. | stdio |
| JOBZYN_API_KEY | Yes | Your JobZyn company API key. Required to authenticate requests to JobZyn. | |
| MCP_AUTH_TOKEN | No | Separate bearer token for HTTP mode, at least 32 characters. Required when MCP_TRANSPORT=http. | |
| JOBZYN_BASE_URL | No | Upstream integration root; HTTPS required, except HTTP on loopback for tests. | https://www.jobzyn.com/api/integrations |
| MCP_ALLOWED_HOSTS | No | Comma-separated exact hostnames/IPs, no scheme or port; required for non-loopback binding. | |
| MCP_ALLOWED_ORIGINS | No | Comma-separated exact browser origins; empty rejects all requests that include Origin. | |
| JOBZYN_REQUEST_TIMEOUT_MS | No | Deadline for headers and response body, 1–300000 milliseconds. | 30000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jobzyn_create_jobA | Create a job (POST /job, write scope). Requires job.id and job.title. Defaults to PUBLISHED: the job becomes public immediately. Set status UNPUBLISHED for a draft. Duplicate external IDs return 409. Additional job fields are preserved. |
| jobzyn_update_jobA | Update a job by external ID (PUT /job/{externalJobId}, write scope). Only supplied fields change. If the job does not exist, JobZyn creates it (201); include a title for creation. Can publish/unpublish through status. Job fields including optional id and custom fields are forwarded as supplied. |
| jobzyn_unpublish_jobA | Unpublish a job by external ID (DELETE /job/{externalJobId}, write scope). Removes public visibility while retaining the job data. Does not permanently delete the job. |
| jobzyn_get_candidatesA | Retrieve one page of applications for an external job ID (GET /job/{externalJobId}/candidates, read scope). Supports since/from/to ISO dates and page/pageSize (1-based; default 50, max 100). since takes priority over from. Use total to fetch remaining pages. Contains personal information and resume URLs; no files are downloaded. |
| jobzyn_link_external_idsA | Link external ATS IDs to existing internal numeric JobZyn job IDs (POST /job/link, write scope). Existing external IDs are not overwritten. Inspect every result: linked, already_linked, or not_found. A batch can partially succeed. |
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 has a distinct primary purpose: create, update, unpublish, fetch candidates, and link IDs. The only mild ambiguity is that update_job can also publish/unpublish via status, which overlaps with unpublish_job, but the dedicated unpublish action is still clearly differentiated.
All tools follow a consistent verb_noun snake_case pattern with the jobzyn_ prefix (create_job, update_job, unpublish_job, get_candidates, link_external_ids). No mixed conventions or vague verbs.
Five tools is well-scoped for a focused job-posting and candidate-retrieval MCP server. Each tool earns its place, and the count is neither too thin nor bloated.
The set covers create, update, unpublish, and candidate retrieval, but lacks a get_job or list_jobs operation, making it impossible to read or verify a job's current details or status through the MCP surface. This is a notable gap for a job-management server.