Claude connector · Chrome extension

Apply to jobs by pasting a link.

Paste a posting into Claude. The Appwing extension fills the application form from your profile, Claude writes only the answers that need judgement, and nothing is submitted until you approve a screenshot of the finished form.

Greenhouse, Lever, Ashby, Workday, Workable and more.

  • Identity-only OAuth
  • The server never reads your email
  • No trackers, no ads, no data sales
An illustration, not a screenshot, of what Appwing puts on a job posting. A Greenhouse application form has five fields Appwing filled — full name, email, two work-authorization questions and an open-ended answer — each marked with a solid rule. A sixth, "Which office would you prefer?", is marked with a dashed rule and left blank. A panel in the corner reads "Filled 5 of 6 fields — 1 needs your input" and names the unanswered question. Along the bottom, the form is held with a "waiting for your approval" label beside an approve and submit button.
How it works

Three things happen, and one of them is you.

The work is split by who is good at it: a deterministic filler for facts, a model for judgement, and a human for the decision to send.

The extension fills

Name, contacts, locations, work authorization, sponsorship, EEO, the dropdowns every ATS words differently — filled straight from your profile by code, not by a model. Same input, same answer, every time.

Claude judges

That leaves the questions a lookup cannot answer — why this team, what you'd bring, how you'd frame six years of scope in four lines. Claude writes those from your profile and the posting in front of it.

You approve

Then it stops. You get a screenshot of the completed form and the last word on it — send, edit, or cancel. Captchas and logins are always handed back to you rather than worked around.

Appwing never submits on its own. There is no setting that turns this off.

Tailored resumes

A resume that structurally cannot lie.

Every tailored resume is rebuilt from the profile you gave us and then checked back against it, line by line, before it is allowed out. A claim with no source in your own material is not softened or hedged — it is removed, and the resume is rejected if it cannot be.

  • It can select, order and rephrase what you already told us for the posting in front of it
  • It cannot add a title, a date, a metric or a tool that is not in your profile
  • Dates, employers and job titles are copied, never generated
  • You see the finished document before it is attached to anything
An illustration of the resume validator: a two-column table pairing each line of a tailored resume with the profile field it came from. "Staff Engineer, Payments — Northwind" traces to the title and employer of the second experience entry; "Cut checkout latency 42 percent" traces to a bullet on that same entry; the skills line traces to the skills list. A fourth line, "Led a team of 12 engineers", has no source in the profile and is struck through and marked removed. A footer reads "3 of 4 lines verified, 1 removed".
Tracker

Everything you sent, on one board.

Each approved application lands in a tracker with the posting, the exact answers that were sent, the tailored resume, and the approval screenshot. A Kanban pipeline moves it along from applied to offer.

  • Drag a card, or just tell Claude "I heard back from Acme"
  • Every status change keeps a timestamped timeline entry
  • Ask "what needs a follow-up?" and get the list
  • The screenshot you approved stays attached to the application
An illustration of the application tracker as a Kanban board with four columns. "Applied" holds seven applications, three of them shown: Staff Engineer at Northwind, Backend Engineer at Globex, Platform Engineer at Initech. "Screening" holds three, including Senior SRE at Acme. "Interview" holds two, with Staff Engineer at Hooli highlighted as the card being moved. "Offer" holds one, Principal Engineer at Stark.
Privacy

Plainly: what we hold, and what we never touch.

This is the short version, in the same words as the policy. Nothing here is a promise the architecture does not already keep.

Identity-only sign-in

Google OAuth with the identity scopes and nothing else — openid, email, profile. We ask for no permission that could read anything of yours.

The server never reads your email

Appwing holds no Gmail credential and requests no Gmail scope. If you connect Gmail to Claude, that link is between you and Anthropic; Appwing only stores what Claude writes into your tracker.

No trackers, no ads, no data sales

There is no analytics script on this page and no third-party code in the extension. Your profile and resume are never sold, shared or used to train anything.

Nothing is sent without you

Applications are submitted only after you approve the screenshot. Captchas and logins are handed back to you. Deleting your data deletes it.

Read the full privacy policy

Setup

Connect it once. Then just paste links.

Two installs and a profile. The connector gives Claude the tools; the extension is what touches the form.

Add the connector

In Claude Code:

claude mcp add --transport http appwing https://mcp.appwing.us/mcp

On Claude Desktop or claude.ai: SettingsConnectorsAdd custom connector, and paste the same URL — https://mcp.appwing.us/mcp

Claude opens a Google sign-in the first time you use it. Identity scopes only.

Build your profile

Sign in and upload a resume. Appwing reads it and then asks only for what is still missing — the work-authorization and demographic answers every application wants and no resume contains.

Open the dashboard

Install the extension

Chrome, unpacked for now. Unzip it, open chrome://extensions, turn on Developer mode, click Load unpacked and select the appwing-extension folder.

Download the extension

Then just say

Apply to this job: <paste the job link>

Claude opens it, the extension fills it, you approve the screenshot, it submits. Worth asking too: "What's in my pipeline?" and "Which applications need a follow-up?"

FAQ

Questions people actually ask.

Can it submit an application without me?

No. The submit step is gated on your approval of a screenshot of the filled form, and there is no configuration that removes the gate. If you close the tab, nothing is sent.

Which application sites does it handle?

Greenhouse, Lever, Ashby, Workday, Workable and a growing list of others. The extension only runs on the sites in its manifest — it is not loaded on any other page you visit.

Can Claude invent things on my resume?

Not through Appwing. Tailored resumes are validated line by line against the profile you supplied, and a line with no source is removed rather than rewritten. It can choose and rephrase your experience; it cannot add to it.

Do you read my email to track applications?

No. Appwing holds no Gmail credential and requests no Gmail scope. If you have Gmail connected to Claude, Claude can read it and record what it finds in your tracker — that connection is yours, not ours.

Why is the extension a zip instead of a store listing?

It is pre-review. Download it and load it unpacked with Developer mode; a Chrome Web Store listing replaces this step when review completes.

What happens to captchas and logins?

They are handed straight back to you. Appwing does not attempt to solve a captcha or type a password, and it never sees your passwords — sign-in to Appwing itself is Google OAuth.

Stop filling in the same six fields.

Build the profile once, connect Claude, and apply by pasting a link. You approve every application before it goes.