Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Job-o-Matic is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Local career database your AI keeps current and writes résumés from.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user job-o-matic-mcp '--' uvx --from job-o-matic job-o-matic-mcp
# 2 — ask your agent for something these tools do
# get_profile, search, resume_data and 12 more
Job-o-Matic costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Job-o-Matic as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user job-o-matic-mcp '--' uvx --from job-o-matic job-o-matic-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take JOBOMATIC_DB (Path to your Job-o-Matic database file (optional; default is your user data folder).), JOBOMATIC_HOME (Folder for your Job-o-Matic data (optional).) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
The whole profile in one call: person, links, employers, positions, items (each with its metrics and attached original ids), resume lines, skills, education. Items hold every kind: responsibilities, achievements, awards, projects, reviews ...
Takes no parameters.
Ranked full-text search over facts, resume lines, employers, positions, items, item metrics, skills and Q&A; best match first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| limit | integer | no | — |
| include_unanswered | boolean | no | — |
The whole resume for a track in one JSON document: person, links, employers (each with its positions, and each position with its ranked lines, the item and metrics behind each line), items (awards, projects, reviews ... with metrics), Verified skills and education. Use it to write a resume or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| track | string | no | — |
Plain-language description of every table, view, column and rule. Read this first.
Takes no parameters.
List rows of a table (optionally only one status), newest ids last. Max 500 rows. Images omit the picture bytes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| table | string | yes | — |
| status | string | no | — |
| limit | integer | no | — |
Fetch one row by id, with created_by and last_changed_by (user, ai or app, from audit); images omit the picture bytes. updated_by is always empty once a write is recorded: read these two instead. Also gets one audit entry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| table | string | yes | — |
| id | integer | yes | — |
Insert a row (no 'id' key) or update one (with 'id'); only editable columns are accepted. Recorded as 'ai'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| table | string | yes | — |
| row | object | yes | — |
| expected_updated_at | string | no | — |
Save many rows of one table in one transaction: all are written or none, and the error names the failing row.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| table | string | yes | — |
| rows | array | yes | — |
Retire a row (status Deprecated / Archived / Retired). Rows are never deleted. Recorded as 'ai'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| table | string | yes | — |
| id | integer | yes | — |
List the unedited source documents (resumes, reviews, ...) with their extraction state. Waiting for you = extracted <> 'Done' ('Text read' means the text is ready but no facts were taken yet).
Takes no parameters.
Store a file from this computer (give its full path) as an original: copied into my_data/originals/, never changed, and its text extracted, the same as Upload in the app. kind: Resume, Job description, Review, Recommendation, Other, or 'AI output' for a file you wrote. PDF, DOCX, TXT, MD, PNG or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| kind | string | yes | — |
| title | string | no | — |
Return an original's metadata and its extracted text. If not extracted yet, says so instead of text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | — |
Record how far facts have been pulled from an original into the tables: 'Not yet', 'Text read', 'Partly' or 'Done'. Set 'Done' only when you have taken everything useful.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | — |
| state | string | yes | — |
Interview questions still waiting for an answer or a review, in order.
Takes no parameters.
Fill a resume template (executive, navy_bar, two_column, structured or genz) with the profile's Short and Long lines for a version (track); Story lines are for cover letters and interviews and are never printed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| template | string | yes | — |
| track | string | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Job-o-Matic or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_profile | no tags | |
| search | no tags | |
| resume_data | no tags | |
| schema_guide | no tags | |
| list | no tags | |
| get | untrusted-input | untrusted-input: keyword "fetch" |
| save | no tags | |
| save_many | no tags | |
| retire | no tags | |
| list_originals | no tags | |
| add_original | no tags | |
| read_original | no tags | |
| mark_extracted | no tags | |
| qa_open | no tags | |
| build_resume | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Job-o-Matic can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.