Job search automation, auto apply, resume builder, application tracking, and recruiter outreach
The official MCP server for JobGPT — auto apply & search jobs, generate and manage custom tailored resumes, and track applications directly from Claude, Cursor, Windsurf, and any MCP-compatible AI tool.
Ask your AI assistant things like:
The MCP server connects your AI assistant to the full JobGPT platform — 34 tools covering job search, applications, resumes, outreach, and more.
There are two ways to connect, depending on your AI tool:
codex mcp login), and ChatGPT Web (Developer Mode).sk_)The browser-login method does not need this — it fetches your key for you after you sign in.
Recommended — browser login (no API key, no JSON):
JobGPT and enter the URL https://mcp.6figr.com/mcpNo terminal, no config file, no Node.js. This uses OAuth, so your API key never touches Claude's config — Claude gets a scoped token instead.
Alternative — API key via mcp-remote (for older Claude Desktop builds that don't show Connectors; requires Node.js 18+):
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"jobgpt": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.6figr.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer your-api-key-here"
}
}
}
}
Recommended — browser login (no API key): add the server, then authenticate in your browser:
claude mcp add jobgpt -t http -u https://mcp.6figr.com/mcp
Then run /mcp inside Claude Code, select jobgpt → Connect, and sign in to 6figr when the browser opens. Claude Code stores a scoped OAuth token — no API key needed.
Option A: One-liner with an API key (claude mcp add):
claude mcp add jobgpt -t http -u https://mcp.6figr.com/mcp --header "Authorization: your-api-key-here"
Option B: Edit settings.json manually
Add to ~/.claude/settings.json:
{
"mcpServers": {
"jobgpt": {
"type": "http",
"url": "https://mcp.6figr.com/mcp",
"headers": {
"Authorization": "your-api-key-here"
}
}
}
}
Recommended — browser login (no API key): add the server, then authenticate in your browser:
codex mcp add jobgpt --url https://mcp.6figr.com/mcp
codex mcp login jobgpt
codex mcp login opens a browser to sign in to 6figr and approve access; Codex stores a scoped OAuth token (OAuth 2.1 + PKCE). No API key needed.
Alternative — API key via header:
codex mcp add jobgpt --url https://mcp.6figr.com/mcp --header "Authorization: Bearer your-api-key-here"
ChatGPT connects two different ways depending on where you add the server:
ChatGPT Desktop app — API key. Open Settings → Connectors → Advanced/Developer → Connect to a custom MCP and fill in:
JobGPTStreamable HTTPhttps://mcp.6figr.com/mcpAuthorization, Value Bearer your-api-key-hereThe desktop dialog authenticates by header (there's no browser-login button), so use your sk_ key here. Leave the env-var fields blank.
ChatGPT Web (Developer Mode) — browser login (OAuth). On the web app, enable Settings → Connectors → Advanced → Developer mode, then Add custom connector, name it JobGPT, and enter the URL https://mcp.6figr.com/mcp. ChatGPT runs the OAuth flow: sign in to 6figr in the popup and approve. No API key needed. (Developer mode is available on Plus, Pro, Business, Enterprise, and Edu plans.)
Go to Settings > MCP > Add new MCP server, or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"jobgpt": {
"type": "http",
"url": "https://mcp.6figr.com/mcp",
"headers": {
"Authorization": "your-api-key-here"
}
}
}
}
Go to Settings > Cascade > MCP > Add Server > Add custom server, or add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"jobgpt": {
"type": "http",
"url": "https://mcp.6figr.com/mcp",
"headers": {
"Authorization": "your-api-key-here"
}
}
}
}
Open the Cline MCP settings in VS Code and add:
{
"mcpServers": {
"jobgpt": {
"type": "http",
"url": "https://mcp.6figr.com/mcp",
"headers": {
"Authorization": "your-api-key-here"
}
}
}
}
Add to your Continue config (~/.continue/config.yaml):
mcpServers:
- name: jobgpt
type: http
url: https://mcp.6figr.com/mcp
headers:
Authorization: "your-api-key-here"
If you prefer to run the server on your machine (requires Node.js 18+):
{
"mcpServers": {
"jobgpt": {
"command": "npx",
"args": ["-y", "jobgpt-mcp-server"],
"env": {
"JOBGPT_API_KEY": "your-api-key-here"
}
}
}
}
| Tool | Description |
|---|---|
search_jobs | Search jobs with filters — titles, locations, companies, skills, salary, remote, H1B sponsorship |
match_jobs | Get new job matches from a saved job hunt (only unseen jobs) |
get_job | Get full details of a specific job posting |
| Tool | Description |
|---|---|
get_profile | View your profile — skills, experience, work history, education |
update_profile | Update name, headline, location, skills, experience |
get_salary | Get your current compensation details |
update_salary | Update base salary, stocks, bonus, target salary |
get_currencies | List supported currencies (for salary updates) |
get_credits | Check your remaining credits balance |
| Tool | Description |
|---|---|
list_job_hunts | List your saved job hunts with credits balance |
create_job_hunt | Create a new job hunt with search filters and auto-apply settings |
get_job_hunt | Get details of a specific job hunt |
update_job_hunt | Update filters, auto-apply mode, daily limits, status |
| Tool | Description |
|---|---|
get_application_stats | Aggregated stats — counts by status, auto-apply metrics |
list_applications | List applications filtered by job hunt or status |
get_application | Get full application details |
update_application | Update status or notes |
apply_to_job | Trigger auto-apply for an application |
add_job_to_applications | Save a job from search results to your applications |
import_job_by_url | Import a job from any URL (LinkedIn, Greenhouse, Lever, Workday, etc.) |
| Tool | Description |
|---|---|
list_resumes | List your uploaded resumes |
get_resume | Get resume details and download URL |
delete_resume | Delete an alternate resume |
upload_resume | Upload a resume from URL (PDF, DOC, DOCX) |
list_generated_resumes | List AI-tailored resumes created for applications |
get_generated_resume | Get a generated resume's download URL |
generate_resume_for_job | Generate an AI-optimized resume for a specific application |
calculate_match_score | Calculate resume-to-job match score with skill analysis |
| Tool | Description |
|---|---|
get_job_recruiters | Find recruiters associated with a job |
get_job_referrers | Find potential referrers at a company |
get_application_recruiters | Get recruiters for a saved application |
get_application_referrers | Find referrers for a saved application |
list_outreaches | List your sent outreach emails |
send_outreach | Send an outreach email to a recruiter or referrer |
| Variable | Required | Default | Description |
|---|---|---|---|
JOBGPT_API_KEY | Yes | — | Your API key from 6figr.com/account |
JOBGPT_API_URL | No | https://6figr.com | API base URL |
DEBUG | No | false | Enable debug logging to stderr |
Your API key isn't being passed to the server. Make sure it's in the env block of your MCP config.
Your API key is invalid or expired. Generate a new one at 6figr.com/account.
Some operations (auto-apply, resume generation) consume credits. Purchase more at 6figr.com/jobgpt.
node --version)JOBGPT_API_KEY=your-key npx jobgpt-mcp-serverAdd "DEBUG": "true" to your env config to see detailed API request/response logs in stderr.
git clone https://github.com/6figr-com/jobgpt-mcp-server.git
cd jobgpt-mcp-server
npm install
cp .env.example .env # add your API key
npm run dev:local # run stdio server locally
npm run build # compile TypeScript
npm run dev:worker # run Cloudflare Worker locally
npm run deploy # deploy to Cloudflare Workers
npx @modelcontextprotocol/inspector
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y jobgpt-mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-6figr-com-jobgpt-mcp-server": {
"command": "npx",
"args": [
"-y",
"jobgpt-mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencejobgpt-mcp-servernpmJobGPT - Job Search Automation & Auto Apply works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.