Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated yesterday
Install
ApplyWise
Overview
Description from the maker (original English)
Job search and form filling; dry run by default, real submits need your approval or consent.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"applywise": {
"command": "uvx",
"args": [
"applywise"
]
}
}
}Run this in your terminal
claude mcp add applywise -- uvx applywiseOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"applywise": {
"command": "uvx",
"args": [
"applywise"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"applywise": {
"type": "stdio",
"command": "uvx",
"args": [
"applywise"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account tanmayagrawal21, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Search & AI memoryi
- More stars than 0% of the other 5653 servers in this category
- Published to the registry more recently than 72% of the other 5653 servers in this category
- Basic checks equal to or better than 100% of the other 5653 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is ApplyWise safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 15 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 21 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated 2 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
job-apply-mcp (ApplyWise)
An MCP server that finds jobs and fills applications for you, and stops before anything irreversible. It is modular (pluggable platforms, LLM providers, browser drivers), parallel, token-frugal (compact, paginated output) and local-first (routine form fields go to Ollama, LM Studio or MLX on your machine; only hard prose escalates). Works with any MCP client on macOS, Linux and Windows.
[!WARNING]
Alpha. Field results from the first live dogfooding run (one user, one night, ~330 discovered postings):
search, ranking, dedupe and planning work end to end, and the browser driver now fills and verifies
complete Greenhouse and Lever forms, but no application has yet been submitted unattended. Most
Greenhouse boards are reCAPTCHA-protected, so the tool fills the form and hands the final click to you
(
handoff), which is the intended behaviour. Free-text questions needwriting.reviewer = "router"(local strict
review) to go out without you. Expect rough edges; every irreversible step is gated, logged and
never retried when the outcome is uncertain.
Install as a Claude Code plugin
The repository is also a Claude Code plugin marketplace. The applywise plugin starts the MCP server for you (pinned to a reviewed version) and adds a skill that tells Claude how to use the tools safely:
claude plugin marketplace add tanmayagrawal21/job-apply-mcpclaude plugin install applywise@applywise
Then run init and doctor from the quickstart below in your own terminal, and check /mcp for plugin:applywise:applywise. The same safety model applies: dry run by default, a human approves every real submit, and visible CAPTCHAs always come back to you; logins, codes and account creation stay with you unless you open a consent window yourself (safety model, items 7 and 8). To update, run claude plugin update applywise@applywise. How releases and the version pin work: docs/release.md.
5-minute quickstart
You need uv (or pipx). No clone required.
# 1. Create config.toml, profile.toml, controls.toml (asks a few questions; --yes to skip them)uvx --from git+https://github.com/tanmayagrawal21/job-apply-mcp job-apply-mcp init
2. Put your real details in the profile it printed the path of, then check everything
uvx --from git+https://github.com/tanmayagrawal21/job-apply-mcp job-apply-mcp doctor
3. Add the printed snippet to your MCP client (guides for ten clients: docs/clients/)
claude mcp add --transport stdio job-apply -- uvx --from git+https://github.com/tanmayagrawal21/job-apply-mcp job-apply-mcp
Then ask your assistant: "search jobs at greenhouse:examplecorp for data roles, plan the best one, and do a dry run." Everything is a dry run until you set dry_run = false.
Install alternatives: pipx install git+https://github.com/tanmayagrawal21/job-apply-mcp (then the command is just job-apply-mcp), or pip install into a virtualenv. After the first PyPI release, uvx applywise (the PyPI distribution is applywise; the job-apply-mcp command stays as an alias). Optional extras: [browser] (Playwright), [agent], [jobspy], [mlx], [hf], [litellm], [keyring].
Features
| Area | What you get |
|---|---|
| Discovery | Parallel search over Greenhouse, Lever, Ashby, SmartRecruiters, Workday and JobSpy boards, paginated |
| Policy gates | Skip by sponsorship, citizenship, clearance, experience, graduation window, salary floor, employer patterns |
| Runs | run_applications / job-apply-mcp run: links you pass, job links you emailed yourself (read-only mail) and discovery in one run, a run report and feedback applied to the next run |
| Applying | Platform API where possible, browser driver otherwise, generic LLM-assisted adapter for other sites |
| Local LLM routing | Complexity-scored tiers (small/medium/large/narrative), fallbacks, optional cloud, your MCP client as last resort |
| Profile builder | Collects the questions your profile could not answer, ranks them, and asks you (profile_questions, answer_profile_question, job-apply-mcp profile ask); the model never supplies an answer |
| Authorization | Per-country facts ([authorization] for your home_country, [authorization. ] for others); no default country, and unknown countries stay unresolved |
| Writing | Cover letters and answers with style rules, banned phrases and gap-avoidance checks |
| Provenance | Every generated text is recorded and can be verified or edited by you |
| Dedupe | Store of applications plus optional confirmation-email ingest so you never apply twice |
| Control layer | Quotas, mode switch, attestation and recipient guards, prose lint, prompt-injection screen |
| Transports | stdio (default) and streamable HTTP with bearer token |
| Operations | init, doctor, Dockerfile, CI on Linux/macOS/Windows |
Run statuses
Every posting in a run_applications / run_report result has exactly one status, with a why where useful (ADR-0049):
| Status | Meaning |
|---|---|
submitted | Live submit sent; a confirmation may follow |
confirmed | Reconciliation confirmed the submission |
dry_run_ok | Dry run complete: a live run would submit it (see live_preview for quotas; the row's captcha mode says whether a captcha would stop it: docs/tools.md) |
needs_human | You must act; why says what (unresolved fields, review gate, awaiting approval, verification code) |
quota_blocked | A daily, per-platform or per-run quota refused the live submit; nothing was sent |
skipped | Not attempted; why says why (policy, duplicate, prose not approved yet, max_applications reached) |
unsupported_site | No enabled adapter handles the host |
unknown | Outcome unclear (for example a roadblock after the click); verify by hand |
failed | An error |
max_applications (a whole number >= 1) caps the eligible postings a run handles (ready to submit, or needing you), the same in dry and live mode; skipped and unsupported postings do not count. A dry run also returns live_preview with what the current live quotas would allow. Live submits also count against the daily (25 per rolling 24 h), per-platform (10) and per-run (10) limits; a user config can lower or raise them.
Safety model
- Dry-run by default.
dry_run = trueunless you change it;initalways writes it. - Approval tokens.
plan_applicationreturns a token bound to a hash of the exact answers. A real submit needs that token, so what you reviewed is what is sent (apply.auto_approveturns this off; do not). - Control layer. Independent checks run before every side effect: daily and per-run quotas, single-submit guard, recipient deny-list, prose lint, page-text injection screen,
apply_enabledkill switch. Add your own rules incontrols.toml. - Hard stops. Visible CAPTCHA challenges and attestation checkboxes matching
policy.stop_phrases(for example "no AI used") always returnneeds_human. They are not configurable away. Verification codes are entered only when the USER types them, confirms a granted prefill (ADR-0026/0027), or consented to unattended runs from a terminal (item 8). Account creation is off by default; it needsaccounts.auto_create = truein your own user config file AND an open credentials consent window (ADR-0046). - No invented facts. Answers come from your profile or are marked; unresolved required fields stop the run. Autonomy level (ADR-0052).
[answers] autonomyin your own user config decides what the agent may assume when you are not available:strict(default: every unresolved field waits for you),safe_default(decline contact/marketing permission, the configured "how did you hear" default, "decline to self-identify"), orinfer(also skill/experience questions about a tool or technology, answered from your resume: Yes only when it clearly says so, otherwise No; willingness, availability, location and terms questions are never inferred). Authorization/visa/identity, background and other screening, accommodation, recording, attestations, legal agreements and employment terms, salary without a policy, start date and location facts are never assumed. Every assumed answer is labelled (assumed, plan, evidence, run report); afterpromote_after(3) assumptions of one question you are asked once and your answer is reused. A project file or env var can only make the level stricter.initasks which level to use;control_statusshows it. - Privacy. Profile and secrets stay on your machine, are never committed, and API keys are read only from the environment. See SECURITY.md.
- Credentials never reach the model. ATS logins live in the OS keychain (
job-apply-mcp vault add --username U, password prompted without echo). The browser fills them straight into the page; MCP exposes onlyvault_status(hosts, never secrets). At most 2 sign-in attempts per host per run; a lockout or wrong password stops that host (ADR-0046). - Consent window (optional, ADR-0048).
job-apply-mcp consent --for 24h(or--per-run,--max N,--scopes ...) is typed once, in a terminal, per period you choose. Inside the window submissions are approved automatically (logged with the consent id), a page whose only bot check is an invisible widget is submitted with one click, and an emailed code is read from the newest message of the expected sender and entered once. Unattended codes stay off untilverification.trusted_authserv_idslists your own mail server's Authentication-Results id (user config only), so a spoofed sender cannot supply a code. You review the results afterwards (list_applications).consent --revokeends it;consent_status(MCP) is read-only and no tool can create one. - Owner-only questions (ADR-0050). Contact, messaging and marketing permissions (SMS, WhatsApp, calls, email, job alerts, talent community) are never answered Yes; only your own
optin:answer applies, and only to a single, plain permission question. Otherwise they stay with you, or are declined (labelledassumed) atanswers.autonomy = "safe_default"or"infer"(item 5). Authorization and sponsorship come only from structured per-country facts. - You make the final click (optional, ADR-0058). Set
[browser] final_click = "human"withheadless = false. The agent fills and verifies each form, brings the tab to the front, and never clicks Submit. You click. A watcher reads the page every 3 s, for up tohuman_click_timeout_s(900 s by default), and records the submission once the site shows its success page.run_applicationsthen hands you one filled tab at a time. The setting only tightens: any config layer can sethuman, and only your own user config can switch it back toagent.
Known limitation: Ashby with reCAPTCHA Enterprise. Ashby forms protected by reCAPTCHA Enterprise silently reject or challenge automated submit clicks, even when the widget is invisible. Use final_click = "human" for these postings.
Transports
job-apply-mcp # stdio (what clients launch)job-apply-mcp --transport http --host 127.0.0.1 --port 8765 # http://127.0.0.1:8765/mcp JOB_APPLY_MCP_TOKEN=... job-apply-mcp --transport http --host 0.0.0.0 # non-local: token required
HTTP binds loopback by default; any other address refuses to start without JOB_APPLY_MCP_TOKEN (Authorization: Bearer ...). Use a TLS reverse proxy for network access. A Dockerfile is included (no browser by default; --build-arg BROWSER=1 adds Playwright and Chromium).
Do
Only the beginning is shown; read the rest in the repo