AIAPPLYD
Confirmed, not assumed

Auto-apply that endson an interview.

You uploaded your resume. Then the form asked you to type it all in again. We do that part, on the company’s own site. It counts as sent when they write back.

Let it apply for meWatch it apply

Upload once. Never type it again.

You upload one resume

One PDF, once. That is the last time your own history goes through a keyboard.

We pick and rewrite

We find the ones you can win and rewrite the resume for each. Only work you did.

They confirm it landed

We fill in their form and press submit. Their email marks it done, not our click.

aiapplyd.com/dashboard

Today's agent run

Applying to Customer Support Manager at Linear

Where your applications actually land
On the company’s own hiring page.
We fill in the real form and you never see it. The next thing you touch is their reply.
1
Resumes you upload. Ever.
0
Forms you fill in yourself
$0.31
What one finished application costs you

Your whole job search, in one place.

Six things happen here. Five of them happen without you.

Best shot first

Smart Job Matching

Every opening from Greenhouse, Lever, LinkedIn and Indeed, held up against what you have actually done. The ones you can win come first.

Find the ones worth it
Submitted, not drafted

AI Auto-Apply

It rewrites the resume, writes the letter, fills in every field and presses submit. You find out about it when they reply.

Let it apply for you
Only things you did

Resume and Cover Letters

One master resume in. A version per posting out, built only from work you did. It is hard-blocked from writing “passionate about”.

Tailor it per job
Checked before you apply

Skip the Ghost Jobs

Reposted every month since March. Open eleven months. Filled internally in week two. We check for the tells before it reaches you.

See what gets flagged
Written by them

Replies Land Here

Anyone can tell you they clicked submit. This is the company itself, in its own words, sorted into invites, confirmations and next steps.

See replies land
Applied to offer

Application Tracking

Applied to offer on one board. Who replied, who went quiet on the Thursday. This is the spreadsheet, keeping itself.

See your full pipeline

Forms you have filled a hundred times. Never again.

Greenhouse, Workday, Lever, Ashby. You have never heard of them and you have filled in all of them, at eleven at night, retyping a resume you already uploaded. We do that part now, on the company’s own page, from the first question to the send.

Greenhouse
Lever
Ashby
Workday
iCIMS
Personio
Teamtailor
SmartRecruiters
Recruitee
Breezy
Workable
Rippling
BambooHR
JazzHR
softgarden
15
Hiring systems we apply through
Greenhouse, Workday, Lever, Ashby, Workable, iCIMS and 9 more. Every one finished, first question to send.
1
Ways an application counts as sent
Their email, arriving in the inbox we applied from. Not our screenshot, not our button click, not our log.
0
Things to install
No extension, no browser left open, no password handed over. We apply from our servers while your laptop is shut.

The companies on the other side of those forms.

You never see the software. You see the job, and then, if we did this right, you see a reply.

Use AI Applyd inside ChatGPT, Claude, and Cursor.

Your whole job search, done inside the chat you already have open.

setup message · paste into your agent

Copy this for your agent

Paste it into the chat. It reads the right docs, wires itself up, and reports back.

Set up the AI Applyd MCP server in the client you are running inside, then prove it works.

WHAT IT IS
AI Applyd is a job-search agent. Its MCP server gives you tools to rewrite a resume against one specific posting, pull the real requirements out of a job description, draft a cover letter, build interview prep, translate a resume, search jobs matched to my profile, and start an auto-apply that files a real application on the employer's own hiring system.

WHERE IT LIVES
Server name: aiapplyd
Transport: Streamable HTTP
URL: https://mcp.aiapplyd.com/mcp

There is no API key, no bearer token and no client secret. Do not ask me for one, because none exists. Do not wrap this in npx mcp-remote. Do not use an SSE endpoint.

HOW TO REGISTER IT
Use the line for the client you are actually running inside, at user scope, so it is still there in my other projects.

Claude Code:
claude mcp add --transport http --scope user aiapplyd https://mcp.aiapplyd.com/mcp

Codex CLI:
codex mcp add aiapplyd --url https://mcp.aiapplyd.com/mcp

Cursor, in ~/.cursor/mcp.json:
{ "mcpServers": { "aiapplyd": { "url": "https://mcp.aiapplyd.com/mcp" } } }

Cline, in ~/.cline/data/settings/cline_mcp_settings.json:
{ "mcpServers": { "aiapplyd": { "type": "streamableHttp", "url": "https://mcp.aiapplyd.com/mcp" } } }
The type field is not optional there. Leave it out and Cline falls back to the deprecated transport without telling anyone.

Any other client: read that client's own current MCP documentation and register a remote Streamable HTTP server the way it expects today. Do not rebuild a config shape from memory. These files moved several times this year.

HOW THE SIGN-IN WORKS
OAuth 2.1 with PKCE and dynamic client registration. Nothing runs anonymously and most clients do nothing at all at add time. The first tool call comes back 401 on purpose, a browser opens at mcp.aiapplyd.com, I sign in with Google or a magic link, I approve a consent screen that names the client asking, and your client stores the token. Claude Code can get it over with up front: claude mcp login aiapplyd

HOW TO VERIFY, IN THIS ORDER
1. List my MCP servers and confirm aiapplyd is registered and connected.
2. List its tools and confirm you can see names beginning with aiapplyd_.
3. Call aiapplyd_search_jobs once with a short query.
4. If that comes back 401, I have not signed in yet. Tell me to finish it in the browser, then call the tool again.
5. Tell me which step you reached and what came back.

An empty tool list before I sign in is expected. It is not a failure and it is not a reason to start editing other files.

RULES
Do not touch, reorder or remove any other MCP server in my configuration.
Do not add an Authorization header. Some clients report the whole connection as failed instead of falling back to OAuth.
Do not invent a config key you have not read in that client's documentation.
Claude CodeClaudeChatGPT/CodexCursor

Cline too, and anything else that speaks MCP. Free account, no card, and you sign in the first time it acts for you.

Setting it up by hand? The address ishttps://mcp.aiapplyd.com/mcp
See how it works
// common questions

Yes, it really presses submit.

AI Applyd applies to jobs for you, so your evenings go on preparing for interviews instead of retyping the same history into one portal after another. It reads each posting, rewrites your resume for it, writes the cover letter, answers the open-ended screening questions from your real history, and files the finished application on the company's own hiring system - the software an employer uses to collect and screen applicants. AI Applyd submits on 15 of those systems: Greenhouse, Lever, Ashby, Workday, iCIMS, Personio, Teamtailor, SmartRecruiters, Recruitee, Breezy, Workable, Rippling, BambooHR, JazzHR and softgarden. Nothing is counted as sent until that employer's own system confirms it. Create an account to watch an application get written. Sending requires a paid plan.

Yes, and AI Applyd holds itself to a standard almost nothing else in this category will accept: an application only counts as sent once the employer's own hiring system confirms it, never because a button got clicked. The same rule holds on all 15 hiring systems AI Applyd submits on: nothing is counted as sent until that employer's own system confirms it - Greenhouse, Lever, Ashby, Workday, iCIMS, Personio, Teamtailor, SmartRecruiters, Recruitee, Breezy, Workable, Rippling, BambooHR, JazzHR and softgarden - and in every country. Your dashboard shows it application by application: which ones the employer confirmed, and which are still waiting. AI Applyd does not publish a success rate, because a number with no denominator printed next to it is marketing rather than evidence.

AI Applyd submits it. The application is filled in and sent on the employer's own hiring system, screening questions included, and then AI Applyd waits for that employer's system to confirm it arrived before marking it sent. AI Applyd's own submit click and its own end-of-run screenshot are recorded too, and they are labelled as its own: they describe what AI Applyd did, never what the company received. A tool that shows you the fields it filled is reading its own typing back to you.

AI Applyd submits on 15 hiring systems - the software companies use to collect and screen applications - and every one of them carries live jobs today: Greenhouse, Lever, Ashby, Workday, iCIMS, Personio, Teamtailor, SmartRecruiters, Recruitee, Breezy, Workable, Rippling, BambooHR, JazzHR and softgarden. That is the whole list, named rather than padded, and the same standard holds on all of them: your application goes in complete and tailored on the employer's own system, and it is only counted as sent once that system confirms it. AI Applyd can read and match jobs from more systems than it submits on (23 families in total), so those roles still reach your dashboard - it just tells you which is which rather than faking a confirmation.

Because the employer's own system says so, not because AI Applyd says so. Every application goes out from an email address AI Applyd created for you, so the confirmation a hiring system sends after a submission arrives somewhere it can be read and tied back to that exact application. Your dashboard then shows it row by row: confirmed by the employer, or still waiting. Nothing is quietly promoted from the second to the first. AI Applyd keeps its own records too - the submit its browser watched go through, the screenshot at the end of the run - and labels them as its own, because they describe what AI Applyd did rather than what the company received. A tool that shows you the fields it filled is reading its own typing back to you.

Yes, and the standard is identical in every country. AI Applyd applies based on which system the employer hires on, not where the job sits, so a role in Berlin, London, Toronto or Austin gets the same tailored application on the same 15 hiring systems - and the same rule about what counts as sent. Personio, Teamtailor and Recruitee in particular carry heavy European inventory, so European roles are first-class here rather than an afterthought.

No - AI Applyd never touches your LinkedIn account and never runs in your browser. It refuses the one-click job-board apply buttons as a matter of policy and uploads a real resume to the employer's own hiring system instead, which is both the safer route and the one a recruiter actually reads. No automated connection requests, no bulk profile views, no scraping of search results. Submissions run from AI Applyd's own infrastructure on rotating residential IPs, never from your browser or your session, and they are paced per user - 15 a day on Hired in 30, 50 on Hired Yesterday.

What a recruiter reads is your real career, in your own voice. AI Applyd's cover letters and tailored resumes pull only from what is actually on your resume - no invented skills, no certifications you never earned, no numbers you never gave it - and an anti-cliche filter bans "passionate about", "leveraged", "spearheaded" and "synergies". If it is not in your history, it does not appear in your application.

No - AI Applyd is built to make spraying awkward. Before anything is sent, your resume is scored against that specific posting. Below the fit floor set in your settings the application is skipped and recorded as skipped: nothing is submitted and the company never sees it. What does get sent is rewritten against that posting, with the open-ended questions answered from your actual history, so a hiring team receives one considered application instead of the same PDF forty times. On top of that AI Applyd puts a hard daily ceiling on every account (15 a day on Hired in 30, 50 on Hired Yesterday) and paces submissions per hiring system. Blasting is the easy thing to build and the first thing a recruiter filters out.

AI Applyd tells you exactly why, on the application itself, in plain language: the posting closed before it got there, the site's bot defence held, the form could not be read, the account wall could not be cleared. Billing has exactly one rule and this is it - if a job is already dead before a browser session opens, nothing is spent and your reservation is returned; once a session runs, you are charged for the compute it genuinely used and the unused part of the reservation goes straight back to your balance. A failed run also does not eat your plan's application allowance: the rolling 30-day count excludes failed and skipped runs, so retrying costs you nothing against your cap. And three things that never happen. AI Applyd does not relabel a failure as a send. It does not switch your auto-apply off behind your back. It does not hand the job back to you to go and finish.

AI Applyd encrypts your data while it travels and while it is stored, never sells it, and never uses it to train AI models. It is used to apply to jobs on your behalf, and nothing else. You can delete every byte of it - resumes, application history, screenshots - from your dashboard whenever you want.

Yes, and cancelling AI Applyd is self-serve - Billing in your dashboard, no email to support, no call to book. You get one "before you go" screen and one required question about why you are leaving, and that is the whole of it. Access then runs to the end of the period you already paid for. Weekly or monthly billing, no annual lock-in, no contract.

Stop applying.Start interviewing.

Let it apply for me