Provides read-only and optional write access to a job-search PostgreSQL database, with tools for checking whether a job exists, retrieving and finding jobs, and saving jobs or updating their status and score when writes are enabled.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@JobDBMCP Check if this job already exists: https://example.com/job/123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server providing controlled access to the job-search PostgreSQL database.
The server exposes domain-specific MCP tools for storing, finding, and reviewing job postings over Streamable HTTP. Arbitrary SQL execution is intentionally not exposed.
Python 3.14+
PostgreSQL 18
Docker, to build and run the images
Related MCP server: GetMattered
uv syncSettings come from environment variables. Copy .env.example to .env and fill it in; .env
is not committed.
Variable | Description |
| PostgreSQL connection string for the application role. |
| Bind address, |
| Listen port, |
| Used only when applying migrations, see below. |
The server speaks MCP over Streamable HTTP at /mcp.
uv run jobs-db-mcpIn Docker:
docker build -t jobs-db-mcp .
docker run --rm --env-file .env jobs-db-mcpThe container needs network access to the database.
Tools: create_job, update_job, create_organization, job_exists, get_job,
find_jobs, count_jobs, find_organizations. The server is meant to run locally, without
authentication; the database role it connects as cannot delete anything.
See docs/api.md for their inputs and outputs.
See docs/db.md for the schema.
Migrations are Liquibase formatted SQL changesets under db/changelog/. The runner image adds
the PostgreSQL JDBC driver, which Liquibase 5 no longer ships:
docker build -t jobs-db-mcp-liquibase dbConnection settings come from .env: LIQUIBASE_COMMAND_URL, LIQUIBASE_COMMAND_USERNAME,
LIQUIBASE_COMMAND_PASSWORD, and LIQUIBASE_COMMAND_CHANGELOG_FILE=changelog-master.yml.
Migrations need DDL rights, so they connect as a different role than the server does.
# status of each changeset
docker run --rm --env-file .env \
-v ./db/changelog:/liquibase/changelog -w /liquibase/changelog \
jobs-db-mcp-liquibase status --verbose
# the SQL that would run, for review before applying
docker run --rm --env-file .env \
-v ./db/changelog:/liquibase/changelog -w /liquibase/changelog \
jobs-db-mcp-liquibase update-sql
docker run --rm --env-file .env \
-v ./db/changelog:/liquibase/changelog -w /liquibase/changelog \
jobs-db-mcp-liquibase updateuv run ruff format .
uv run ruff check . --fix
uv run mypy
uv run pytest -qThis server cannot be deployed
Semantic search over 3.5M+ live US job postings pulled straight from company ATSes. Read-only.
A jobs data API and MCP server. Every listing comes from the employer's own career site, an ATS feed or a government employment service, never resold from another board. Each row names its source and when we last confirmed the vacancy existed, and a role that disappears keeps a closure date and a reason. Six tools: search_jobs, get_job, company_hiring, market_signals, coverage, changes_since.
Job search over employers' own hiring systems. Search with no key; a free key opens every read tool.
Live Google for Jobs postings: salary, apply links, remote and date filters. Pay per job.
