Worklittle Jobs

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://mcp.worklittle.com/

claude mcp add --transport http jobs https://mcp.worklittle.com/

{
  "mcpServers": {
    "jobs": {
      "url": "https://mcp.worklittle.com/"
    }
  }
}

{
  "servers": {
    "jobs": {
      "type": "http",
      "url": "https://mcp.worklittle.com/"
    }
  }
}

https://mcp.worklittle.com/

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• search_jobs

  Jobs — 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. PLA

• search_companies

  Jobs — 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

• get_job_details

  Jobs — 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)

• get_market_overview

  Jobs — 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 slic

• track_applied_job

  Jobs — Add a job to the user's Applied or Saved list, or change its status, so they can find it later.

• get_my_profile

  Jobs — 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_chats

  Jobs — List the user's recent Worklittle chats (title and status) for the app sidebar.

• mint_mcp_ui_embed_session

  Jobs — Create a sign-in link so the Worklittle app can open the user's chats on worklittle.com.

• logout_connected_account

  Jobs — Sign the user out of Worklittle in this app.

• upload_my_resume

  Jobs — 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_fi

• get_my_resume

  Jobs — 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_resume

  Jobs — Delete the user's main resume from their profile. Other saved resumes stay.

• update_my_profile

  Jobs — 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_job

  Jobs — 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,

• check_application_status

  Jobs — 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_application

  Jobs — 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_application

  Jobs — 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_application

  Jobs — 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 t

• save_about_me

  Jobs — 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

• list_active_applications

  Jobs — 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_applications

  Jobs — 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, appli

• get_apply_settings

  Jobs — 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_settings

  Jobs — 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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

• ! 注意

  作者与仓库一致

  发布者（worklittle）不是仓库所有者（worklittle）；可能是其他人代为上架的

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 122 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 23 个工具描述，未发现针对 AI 的隐藏指令

与“搜索与 AI 记忆”中的其他服务器比较i

• 星标数多于此分类中其他 5760 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 5760 个服务器的 53% 更新
• 基础检查结果等于或优于此分类中其他 5760 个服务器的 40%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README