FoundRole MCP — Run Your Job Search From Your AI Assistant

Your job search is scattered across a dozen browser tabs, a spreadsheet you forgot to update, and a calendar with no follow-up reminders. FoundRole's MCP server pulls all of it into the AI assistant you already talk to — Claude, ChatGPT, Cursor, and any other MCP client.

Ask in plain language. Your assistant searches live roles, saves the good ones to your tracker, moves them through your pipeline, and sets the follow-up reminders you'd otherwise miss — without you leaving the chat.

Start searching right away — no sign-up needed. Connect your client and ask for jobs immediately. You only sign in (once) when you want to save and track them — and your AI does that for you the moment you ask. Free forever — no API key to manage, no credit card.

What it does for you

• Find roles without tab-juggling — no sign-up. Search FoundRole's live job board by title, location, company, salary, and how recently a role was posted, straight from chat. No account needed — connect your client and start searching.
• See the full picture before you apply. Pull a job's description, requirements, salary, and apply link without opening the page. Also works without an account.
• Stop losing track of applications. Save jobs to your Kanban application tracker and move them through stages (Saved → Applied → Interviewing → Offer) by asking. Attach notes, tags, expected salary, and recruiter contacts. _(One-time sign-in — your AI handles it the first time you save a job.)_
• Research before you commit. Dig into companies, industry sectors, and hiring by location to decide where to aim.
• Never miss a follow-up. Set a reminder on any tracked job and get an email with a calendar (.ics) invite for Google Calendar, Outlook, or Apple Calendar. _(Part of your tracked jobs — uses the same one-time sign-in.)_
• Let the search come to you. Subscribe a saved search to recurring alerts (daily, weekly, or monthly) so new matches land in your inbox. _(One-time sign-in, the same as the tracker.)_

It's the same account and data as FoundRole.com — the MCP server just lets your AI drive it.

New here? The FoundRole AI Search guide walks through connecting each client step by step, with an FAQ.

Setup

Two ways to connect, depending on your client. Either way, searching works the moment you connect — no sign-up. A FoundRole sign-in is only needed for saving and tracking jobs, and your client prompts for it automatically the first time you ask for that.

Option 1 — Direct HTTP (recommended for Claude & ChatGPT)

Point your client at the FoundRole MCP endpoint:

https://www.foundrole.com/mcp

That's it — you can start searching jobs immediately. When you later ask to save or track a job, the client opens a browser window to sign in to FoundRole once, then remembers it.

Option 2 — stdio bridge (for clients without remote HTTP MCP)

Run the proxy locally with npx; it bridges your client's stdio transport to the FoundRole endpoint. Search works straight away; it handles the OAuth sign-in for you only when you first save or track a job:

npx @foundrole/ai-job-search-mcp

Connecting your AI assistant

Claude Web/Desktop

Estimated time: ~2 minutes

1. Open Claude settings (profile / settings icon).
2. Find Connectors (or Tools) and click Add custom connector.
3. Name it FoundRole.
4. In the Remote MCP server URL field, paste:

   https://www.foundrole.com/mcp

1. Save — and start searching jobs right away. The first time you ask Claude to save or track a role, it opens a FoundRole sign-in window; complete it once and you're set.

Claude's custom connectors require a Claude Pro/Team/Enterprise plan on Claude's side. The FoundRole connection itself is free.

ChatGPT

Estimated time: ~3 minutes

1. In ChatGPT, open Settings → Connectors.
2. Click Add custom connector.
3. Name it FoundRole.
4. Paste the server URL when prompted:

   https://www.foundrole.com/mcp

1. Select FoundRole as a source in Deep Research or when enabling connectors — searching works immediately. ChatGPT will prompt you to sign in to FoundRole the first time you ask it to save or track a job.

ChatGPT connectors require a ChatGPT Plus/Team/Enterprise plan on ChatGPT's side. The FoundRole connection itself is free.

Cursor / VS Code / Windsurf

Add FoundRole to your client's MCP config. With the stdio bridge:

{
  "mcpServers": {
    "foundrole": {
      "command": "npx",
      "args": ["@foundrole/ai-job-search-mcp@latest"]
    }
  }
}

Clients that support remote HTTP MCP can instead point directly at https://www.foundrole.com/mcp. Searching works as soon as it's connected; FoundRole sign-in is prompted the first time you save or track a job.

LM Studio

Estimated time: ~3 minutes | Requires: Node.js + npm

1. Open LM Studio's MCP servers configuration.
2. Add this entry:

   {
     "mcpServers": {
       "foundrole": {
         "command": "npx",
         "args": ["@foundrole/ai-job-search-mcp@latest"],
         "env": {}
       }
     }
   }

1. Save and restart LM Studio.
2. Confirm foundrole appears in your MCP servers list — you can search jobs straight away. FoundRole sign-in is prompted the first time you save or track a job.

Perplexity Desktop

Estimated time: ~4 minutes | Requires: Perplexity Pro + Node.js

1. Open Perplexity's MCP configuration.
2. Add:

   {
     "command": "npx",
     "args": ["@foundrole/ai-job-search-mcp@latest"],
     "env": {}
   }

1. Save and restart Perplexity — searching works right away. FoundRole sign-in is prompted the first time you save or track a job.

Perplexity uses stdio MCP transport — Node.js and npm must be installed.

Try saying

• _"Find senior backend engineer roles in San Francisco posted this week."_
• _"Pull the full details and apply link for that Stripe job."_
• _"Save it to my tracker and mark it Applied."_
• _"Add a note that I referred through Alex, and tag it fintech."_
• _"Remind me to follow up next Tuesday morning."_
• _"What's in my Interviewing column right now?"_
• _"Subscribe me to weekly alerts for remote React jobs."_

Security

• OAuth 2.1 with PKCE. You sign in to FoundRole through a standard authorization flow — short-lived tokens, instant revocation, no credentials shared with the AI client.
• HTTPS only, with dynamic client registration and redirect-URI validation.
• Streamable HTTP transport (direct), or stdio via this proxy.

Troubleshooting

Asked to sign in / "needs authentication":

• Expected the first time you save or track a job — searching itself never asks for this. Complete the FoundRole sign-in in the browser window your client opens.
• If saving still doesn't work afterward, reconnect the connector so the authorization is re-sent.

"Connection failed":

• Check your internet connection and that the URL is exactly https://www.foundrole.com/mcp.
• Confirm your client supports remote HTTP MCP; if not, use the stdio bridge (Option 2).

"Command not found" (stdio clients):

• Install Node.js (see engines in package.json for the required version), then retry, or install globally: npm install -g @foundrole/ai-job-search-mcp and run ai-job-search-mcp.

Connector not working:

• Double-check the URL and restart the AI client. If searching works but saving a job doesn't, reconnect to re-trigger the FoundRole sign-in.

Help

• 🌐 Website: www.foundrole.com — free AI job search, application tracker, and company research
• 📖 Setup guide & FAQ: foundrole.com/ai-search-mcp
• 🐛 Issues: GitHub Issues
• 💬 Questions: [email protected]

No account needed to search. Connect your AI client and start finding roles now. Sign up free at FoundRole when you want to save jobs and track your applications — your AI signs you in the first time you ask.

_Made by the FoundRole team._