Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Workopia — Job Search 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
Search 6.3M+ live jobs from companies' own career pages, plus resume tailoring & cover letters.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http workopia-job-search-mcp https://workopia.io/api/mcp-jobs
# 2 — ask your agent for something these tools do
# tailor_resume_tool, cover_letter_tool, job_tool and 2 more
Workopia — Job Search 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http workopia-job-search-mcp https://workopia.io/api/mcp-jobsReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 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.
Tailor a resume to a SPECIFIC job — TWO steps. STEP 1 (default; action omitted or 'prepare'): the server returns the job's full JD, its must-have skills/requirements, and the candidate's current resume, plus tailoring instructions. YOU (the model) then WRITE the tailored resume as JSON Resume, following the instructions — weave JD keywords into existing bullets only where the candidate genuinely h
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | no | ID of a job from a prior search/refine result. Use the Job Id value from the prior search result's content text VERBATIM. Server fetches full JD from Mongo. |
| job_description | string | no | Full JD text when the user pastes it directly (alternative to job_id). |
| job_title | string | no | — |
| company | string | no | — |
| resume_text | string | no | User's resume content (plain text or JSON Resume as string). Fallback when resume_data is not provided. |
| resume_content | string | no | — |
| resume_data | object | no | PREFERRED shape — structured resume per utils/tailor/types.ts ResumeTree. Server, widget, and main-site PDF template all consume this exact shape. Collect these fields from the user before calling whe |
| user_profile | object | no | Optional main-site profile object; used as a fallback source for name/title/contact/experience when resume_data and resume_text are both absent. |
| user_email | string | no | — |
| session_id | string | no | — |
| customization_level | string | no | — |
| action | string | no | Omit or 'prepare' = STEP 1 (server returns JD + resume + instructions for you to tailor). 'save' = STEP 2 (pass tailored_resume; server renders a PDF and saves it to the dashboard; requires sign-in). |
| tailored_resume | object | no | STEP 2 only: the tailored resume you generated, as a JSON Resume object (or a JSON string). The server renders it to PDF and stores it on profile.applications[job_id].resumeTailor. |
| tailor_resume | object | no | Optional wrapper containing the same fields above (legacy shape). |
| parameters | object | no | — |
Write a cover letter for a SPECIFIC job — TWO steps. STEP 1 (default; action omitted or 'prepare'): the server returns the job's JD and the candidate's background, plus writing instructions. YOU (the model) then WRITE the cover letter (250–350 words, specific to the role, mapping the candidate's real achievements to the JD — never fabricate). STEP 2: call this tool again with action:'save', cover_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | no | ID of a job from a prior search/refine result. Use the Job Id value from the prior search result's content text VERBATIM. Server fetches full JD from Mongo. |
| job_description | string | no | Full JD text when the user pastes it directly (alternative to job_id). |
| job_title | string | no | Optional; used in the 'for <role> at <company>' confirmation line. |
| company | string | no | Optional; used in the confirmation line. |
| resume_text | string | no | User's resume content (plain text or JSON Resume as string). |
| resume_content | string | no | — |
| json_resume | object | no | Optional JSON Resume object (basics/work/skills). Takes precedence over resume_text when both present. |
| user_profile | object | no | Optional main-site profile object; used as a fallback source for summary/skills/experience and for the cover letter header (firstName, lastName, email, phone, city, country). |
| user_email | string | no | If provided, server fetches the full Workopia profile for the cover letter header + writes the generated cover letter back to profile.applications[jobId].coverLetter. |
| session_id | string | no | — |
| action | string | no | Omit or 'prepare' = STEP 1 (server returns JD + background + instructions for you to write). 'save' = STEP 2 (pass cover_letter_text; server renders a PDF and saves it to the dashboard; requires sign- |
| cover_letter_text | string | no | STEP 2 only: the cover letter you wrote (plain text). The server renders it to PDF and stores it on profile.applications[job_id].coverLetter. |
| cover_letter | object | no | Optional wrapper containing the same fields above (legacy shape). |
| parameters | object | no | — |
Search jobs across 90+ countries by title, location, salary, remote/hybrid work mode, or employment type. Find roles in tech, finance, product, design, marketing, and every other vertical — aggregated from 1000+ ATS sources globally. Default action is search; use refine when the user asks for more matches or gives feedback on a prior result set; use save to bookmark a job for the signed-in user (r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | Optional; omitted = search. refine = after results/feedback; save = bookmark a job for the signed-in user. |
| search_jobs | object | no | Search args. Required: city. Optional filters surface only when the user explicitly mentions them — omit otherwise. job_title+city uses indexed snapshot; company+city (optional job_title) uses legacy |
| refine_recommendations | object | no | Refine args. Pass exclude_ids (array of Job Id strings from prior result) and session_id always. For 'more like #N': pass liked_indexes=[N] or liked_job_ids=[<Job Id>]. For 'less like #N': pass dislik |
| save_job | object | no | Save args. Required: job_id (from job_cards[].card.id in a prior search result). Optional: job_title, company, job_url. |
| parameters | object | no | — |
Render the full job-detail card for a specific job the user asks about. Use this whenever the user references a particular job from a prior search result — by number (#1, '1', 'first', 'the 3rd one', 'job 3'), by company name (partial or full, e.g. 'Morgan Stanley', 'Morstan'), by role/title phrase ('the analyst role', 'the credit risk one'), or by any 'show me this job' / 'tell me more about X' /
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | no | The id from a prior search result's job_cards[].card.id. Required. |
| get_job_detail | object | no | — |
| user_email | string | no | — |
| parameters | object | no | — |
Show the signed-in user's Workopia dashboard (saved, tailored, and applied jobs + latest resume). Requires OAuth. Default action is list; optional status_filter (all | saved | tailored | applied). Use whenever the user asks to recall their Workopia activity: 'my applications', 'what jobs have I saved / applied to / tailored', 'show my dashboard', 'where did I leave off'. Returns a secure link to o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | — |
| status_filter | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Workopia — Job Search 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 | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| tailor_resume_tool | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| cover_letter_tool | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| job_tool | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| job_detail_tool | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| dashboard_tool | 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.
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
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 Workopia — Job Search 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.