mcp-job-queue
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBQ_DB_PATH | No | SQLite (WAL) queue file | ~/.mcp-job-queue/queue.db |
| JOBQ_LOG_LEVEL | No | debug / info / warn / error | info |
| JOBQ_ARTIFACT_DIR | No | Where result artifacts are written | ~/.mcp-job-queue/artifacts |
| JOBQ_MAX_TIMEOUT_MS | No | Hard ceiling for a per-job timeout | 600000 |
| JOBQ_MAX_CONCURRENCY | No | Max jobs a worker runs at once (backpressure) | 4 |
| JOBQ_POLL_INTERVAL_MS | No | Idle poll interval | 250 |
| JOBQ_DEFAULT_TIMEOUT_MS | No | Default per-job timeout | 30000 |
| JOBQ_RETRY_BASE_DELAY_MS | No | Base delay for exponential backoff | 500 |
| JOBQ_DEFAULT_MAX_ATTEMPTS | No | Default attempts incl. the first | 3 |
| JOBQ_MAX_ATTEMPTS_CEILING | No | Hard ceiling for attempts | 10 |
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 |
|---|---|
| submit_jobA | Enqueue a job for asynchronous execution by the worker. Returns the created job (status 'queued'). Valid |
| get_jobA | Fetch a single job by id, including its status, result, and artifact path. |
| list_jobsA | List recent jobs (newest first), optionally filtered by status. |
| cancel_jobA | Cancel a job that is still queued. Running or already-finished jobs cannot be cancelled and return a NOT_CANCELLABLE error. |
| get_statsA | Return queue health: job counts by status, total, age of the oldest queued job, and the active configuration. No sensitive data. |
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 and clear purpose: submitting, getting, listing, canceling jobs, and fetching queue statistics. No overlap or ambiguity.
All tool names follow the verb_noun pattern (cancel_job, get_job, get_stats, list_jobs, submit_job) with consistent snake_case styling.
With 5 tools covering essential job queue operations, the count is well-scoped and not excessive or insufficient.
The tool set covers all fundamental CRUD-like operations for a job queue: submit, get, list, cancel, and health statistics. No obvious gaps.