MCP/CLI
Tus agentes favoritos ya pueden encargarse de esto.
Toda tu búsqueda de empleo, hecha dentro del chat que ya tienes abierto.
mensaje de configuración · pégalo en tu agente
Copia esto para tu agente
Pégalo en el chat. Lee la documentación correcta, se configura solo y te informa.
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 también, y cualquier otra cosa que hable MCP. Cuenta gratis, sin tarjeta, e inicias sesión la primera vez que actúe por ti.
¿Lo configuras a mano? La dirección es
https://mcp.aiapplyd.com/mcpTodo lo que puedes pedir, en el chat.
Tu cuenta gratuita cubre el emparejamiento, los CV y la preparación de entrevistas. Postularse y las cartas de presentación están en los planes de pago.
Plan de pago
Se postula por ti
Apúntalo a un empleo. Rellena el formulario en Greenhouse, Workday o Lever, con tus palabras, y pulsa enviar.
Nada cuenta como enviado hasta que el empleador lo confirma.
Cuenta gratuita
Tu CV, reescrito para un empleo
Reescrito para la oferta que le indiques, a partir de trabajo que has hecho de verdad. En cualquier idioma.
Cuenta gratuita
Empleos que merecen tu tarde
Ordenados según lo que has hecho de verdad, no según tu título del puesto.
Cuenta gratuita
Listo antes de la entrevista
Las preguntas que hará este puesto, cada una asociada a una historia que ya tienes.
Plan de pago
Una carta que merece enviarse
Tu historial real, la empresa concreta y un filtro que se niega a escribir «me apasiona».
Un agente. Dos formas de entrar.
El MCP remoto funciona desde el chat. WebMCP funciona cuando un agente de navegador compatible ya está en AI Applyd.
MCP remoto
Conéctate una vez desde ChatGPT, Claude, Cursor u otro cliente MCP. Tu agente puede usar AI Applyd sin tener esta página abierta.
WebMCP nativo del navegador
En la prueba experimental de WebMCP de Chrome, un agente que visite AI Applyd puede leer los empleos públicos y los planes. Cuando inicias sesión, puede leer tus coincidencias, los detalles de los empleos y el progreso de tus candidaturas, y guardar un empleo para después.
WebMCP usa la sesión de navegador que ya está abierta en esta página. No sustituye al servidor MCP remoto y no hace que los agentes externos descubran AI Applyd antes de visitarlo.
Lo que pregunta la gente antes de empezar.
The AI Applyd MCP server puts AI Applyd's job-search tools inside your AI assistant, so the chat you already have open can do the work instead of describing it. MCP is the open standard for connecting AI clients to external tools. Once it is connected you can pull apart a job description, rewrite your resume against it, draft the cover letter, translate the resume, prep for the interview and search live matched jobs, all without leaving ChatGPT or Claude. The connection URL is https://mcp.aiapplyd.com/mcp, and every tool runs against your own AI Applyd account.
Any MCP-compatible client can connect to the AI Applyd MCP server. That includes ChatGPT, Claude (Desktop, Code and web), Cursor, Windsurf and Cline. Both transports are supported: Streamable HTTP at https://mcp.aiapplyd.com/mcp for modern clients, and Server-Sent Events at https://mcp.aiapplyd.com/sse for the ones still on SSE.
They are two different ways for an agent to use AI Applyd. The remote MCP server connects AI Applyd to ChatGPT, Claude, Cursor and other MCP clients even when aiapplyd.com is not open. WebMCP is an experimental browser feature: after a compatible agent visits AI Applyd, the page can offer tools through the browser session already open there. Signed-out WebMCP tools can read public jobs and plans. Signed-in tools can read your matches, applications and job details, and save a job. WebMCP is page-bound, so it does not replace remote MCP and does not create off-site discovery by itself.
The AI Applyd MCP server is free to connect, on a free account. There is nothing to buy and no card to enter: you sign in with Google once, and the account starts with 10,000 tokens. Job-description analysis, resume optimization, translation, interview prep and the job match-finder all run on that balance. Cover letters and auto-apply are on a paid plan. Free here means free account, not no account: there is no anonymous tier, and a tool call without a session gets a 401 rather than a result. Top up or upgrade in your dashboard when you want more runs.
Yes, and it is free to create. The first time you ask your assistant for a tool it opens a Google sign-in, no card. That account is what the tools read your profile from and what they spend tokens against, and it starts with 10,000 of them. Every tool is behind it, without exception: an unauthenticated call is answered with a 401 so your client knows to start the login rather than quietly returning nothing. Cover letters and auto-apply additionally require a paid plan.
On a free account, drawing on your 10,000 starter tokens: job-description analysis, resume optimization against a specific posting, resume translation, PDF export, interview question generation, the job match-finder, and your job preferences. On a paid plan: cover letter generation and auto-apply, which files the finished application on the employer's own hiring system. Each tool returns structured results your assistant can read back and act on, so "rewrite this for the Stripe posting and then apply" is one message rather than an afternoon.
Tools spend tokens from the same balance as the web app, so the 10,000 you start with cover your first runs. Tokens are spent on the real compute each run uses, so you pay for what you actually ran. Top up or upgrade in your dashboard when you get low. There is no separate MCP meter and no second bill: one balance, whether the request came from the assistant or the dashboard.
Yes. Data is encrypted in transit (TLS) and at rest, never sold, and never used to train AI on your resume. The account connection uses scoped access, so the assistant only reads what the tool it is running actually needs, and you can disconnect the client or delete every byte from your dashboard whenever you like.