AIApply MCP server

• Addresshttps://aiapply.co/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on aiapply.co when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-26
• Tools14
• Server calls itselfAIApply
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 279 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer336 ms
• Space in an agent's context≈ 3,198 tokensthe definitions of all its tools (14), which an agent carries on every turn
• Tool definitionsA · 99 of 100
• Typed results14 of 14 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 14

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_jobs

  Use this when the user wants current AIApply job listings filtered by role, skills, remote status, or country. Works without an AIApply account: the role is then required, since there is no saved keyword to fall back on. For a signed-in…

• list_review_jobs

  Use this when the connected user wants applications currently waiting for review. Return only job facts and opaque IDs; never submit or change an application. Needs an AIApply account: if the user has not signed in, calling it asks them…

• list_applications

  Use this when the connected user wants recent AIApply application and preparation status. Return role, company, status, match score, timestamp, and canonical listing link without exposing resumes or contact details. Needs an AIApply…

• preview_application

  Use this when the connected user asks what AIApply prepared for one specific application, identified by the job_id returned from list_applications or list_review_jobs. Read the cover letter AIApply wrote, unless it was withheld. This…

• get_auto_apply_preferences

  Use this when the connected user asks about current AIApply job preferences or before suggesting a change. Read target roles, locations, work types, experience, salary, exclusions, daily limit, and application mode without modifying them…

• open_auto_apply_preferences

  Use this when the connected user asks to change their AIApply job preferences — target roles, locations, work types, experience, salary, excluded companies, the daily limit, or how applications are submitted. Nothing here can change them…

• list_unread_mail

  Use this when the connected user asks whether anything new has arrived in their AIApply mailbox, or before telling them about interview invites. Returns unread messages as sender and subject only, with a link to the mailbox. It cannot…

• apply_to_job

  Use this when the connected user wants AIApply to apply to a job they picked from search_jobs. AIApply adds it to their queue already approved, so it does not wait for anyone: it will be applied for and that spends a credit. This is the…

• submit_application

  Use this only when the connected user has asked for one specific job from their review queue to be applied for, identified by the job_id from list_review_jobs. Approving it spends one application credit and cannot be undone: AIApply…

• pause_resume_applications

  Use this when the connected user asks to stop or restart AIApply applying for them. action="pause" stops all automatic applying and is destructive: call it without confirmed, show the user what will stop, ask them, then call again with…

• get_credits_summary

  Use this before queuing or sending work to check the connected user can still pay for it, or when they ask how many applications they have left. Reports the credit balance, whether auto-apply is active, the plan slug and the configured…

• get_setup_status

  Use this when the connected user wants AIApply to apply for them, and again whenever they come back to it: it says what is still missing — their resume, their confirmed job preferences, a plan that includes applying — and next_step names…

• add_resume

  Use this when get_setup_status says next_step is add_resume. Pass exactly one of: resume, the file the user attached, if you can attach files to tool calls; or resume_text, the content of their CV as you can read it, or the work history…

• save_auto_apply_setup

  Use this once the user has seen and confirmed the job titles, location, work mode, job type and experience level AIApply needs: call it with confirmed=true and the values they confirmed, without asking them again. Without confirmed it…