Your favourite agents can already take this over.

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.