Worklittle Jobs MCP server

What tools does Worklittle Jobs expose? (23)

Read from the live server. Click any tool for its input schema.

• search_jobsJobs — Opens the Worklittle jobs MAP for a place and an optional role. This is a map query, not a list of jobs: the map recenters on the place and shows jobs there, so send the place and the role as SEPARATE fields. Never write 'product manager in San Francisco' as one query. PLACE: always pass near_lat + near_lng (the city's coordinates, which you know) and location as the display name (e.g. 'San
• search_companiesJobs — Search the Worklittle market company index by name or slug (ranked typeahead). Returns id, name, slug, logo_url, and enrichment fields for employers with open jobs. Use when the user names an employer and you need a real slug/id for search_jobs company= filters, job alerts, or automations. If zero hits, try alternate spellings or related employer names from further search_companies calls —
• get_job_detailsJobs — Fetch detailed information about a specific job, including full responsibilities, qualifications, and company details. Pass job_id from search_jobs when you have one. If the user asks for full details of a role without an id (e.g. the first software engineer job in Austin), pass query and optional location instead — the tool loads the first matching live listing.
• get_market_overviewJobs — Returns aggregate job-market statistics from Worklittle. Call with no args for the full indexed market (counts, workplace mix, top hiring companies). When the user names a role and/or city (e.g. product managers in San Francisco), pass query and location. The filtered slice includes match count, top companies in the sample, and salary signals from listings that publish pay.
• track_applied_jobJobs — Add a job to the user's Applied or Saved list, or change its status, so they can find it later.
• get_my_profileJobs — Get the user's Worklittle profile (name, location, contact details and job preferences). If they have not linked their account it returns connected false; use get_my_resume or apply_for_job to sign them in.
• list_recent_chatsJobs — List the user's recent Worklittle chats (title and status) for the app sidebar.
• mint_mcp_ui_embed_sessionJobs — Create a sign-in link so the Worklittle app can open the user's chats on worklittle.com.
• logout_connected_accountJobs — Sign the user out of Worklittle in this app.
• upload_my_resumeJobs — Save the resume the user attached in the chat (PDF, Word, text or image) as the main resume on their Worklittle profile so it can be used to apply. It replaces the current main resume; other saved resumes (an account keeps up to 5) stay. Pass the attached file as resume_file.
• get_my_resumeJobs — Get the user's main resume: its status (ready, processing or missing) and, when ready, the resume text and profile details read from it. Use it to tailor advice or an application to the user's real experience.
• delete_my_resumeJobs — Delete the user's main resume from their profile. Other saved resumes stay.
• update_my_profileJobs — Update the user's Worklittle profile, such as name, location, phone, links or the kind of job they want. Only send the fields to change.
• apply_for_jobJobs — Apply to a job for the user: Worklittle fills out and submits the application in a browser. Pass job_id from search_jobs. For a Worklittle-hosted posting also include name, email and resume. It submits by default; pass auto_submit false when the user wants to review first, then show them the answers from check_application_status and send it with submit_application only after they say so.
• check_application_statusJobs — Check an application Worklittle is filling out: its status, which form fields are filled, and a live view link. Only the status completed means it was submitted.
• submit_applicationJobs — Send an application that stopped for review (apply_for_job with auto_submit false, status awaiting_submit). Call it only after the user has seen the answers from check_application_status and said to send it.
• stop_applicationJobs — Stop an application that Worklittle is filling out for the user. This cancels the application in progress and it cannot be resumed; the user would have to start it again. Needs the session_id from apply_for_job or list_active_applications.
• steer_applicationJobs — Change what an application in progress fills in, without stopping it. Use when the user says something about an application Worklittle is filling right now ("say my notice period is one month", "my friend Ana Ruiz referred me", "I need visa sponsorship for the US", "make that answer shorter"). Pass their wish as plain instructions with their exact facts; never add facts. Works while the app
• save_about_meJobs — Save standing facts about the user that Worklittle's Apply with AI uses on every future application: work authorization and visa sponsorship by country, relocation, notice period, desired salary, languages, qualifications, who referred them, or other standing answers they ask applications to use. Stored as the 'More about you' text in their Settings. Pass the complete text to keep (read get
• list_active_applicationsJobs — List the user's applications that Worklittle is filling out right now (queued, running, or waiting on the user), with job_id and session_id. Use it to find which one to stop or check.
• list_applicationsJobs — List applications: pending ones (matched by auto-apply, waiting for approval, running, or waiting on the user) and finished ones (completed = submitted, failed, stopped). Check it before applying so the same job is never applied to twice. Filter with status (pending, applied, ...), job_id or applicant_id.
• get_apply_settingsJobs — Get the user's apply settings: auto_apply (Worklittle applies to matching jobs on its own), auto_submit (submit without a review stop) and tailor_resume (tailor the resume to each job).
• update_apply_settingsJobs — Turn auto_apply, auto_submit or tailor_resume on or off. Only send the settings to change. Turning auto_apply on needs Instant or a card on file.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• Last commit 24 days ago — Actively maintained.
• Repository created 2 months ago — Very new project with little track record yet.
• 0 GitHub stars — Very little community usage so far.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%100%

  Last commit 24 days ago.

• Adoption20%0%

  0 stars.

• Transparency20%100%

  4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

• Provenance15%75%

  Links to its own repository; package linkage unverified.

• Packaging15%75%

  Remote endpoint; authentication requirements not declared.

Maintain Worklittle Jobs? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![Worklittle Jobs on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-worklittle-jobs)](https://mcp-skills-hub.vercel.app/mcps/io-github-worklittle-jobs)