Best for
- Job seekers who want to self-host and control their career data.
- Users who want to record jobs or interview questions without leaving an AI chat.
- Users of AI clients such as Claude Desktop, OpenClaw, or Hermes.
J
JobSync MCP Server
Community
A self-hosted AI assistant for job search and application tracking
GitHub source repository ↗
57FMRS · C
The source presents JobSync MCP as a practical bridge between AI clients and a self-hosted job-tracking application, with local Ollama support as a privacy-oriented option. No concrete MCP tool identifiers or complete permission list are provided, so the tool list is left empty. Protect the access token and review AI-generated results before saving.
JobSync is a free, open-source, self-hosted job search assistant for managing applications, resumes, tasks, and job-search analytics. Its built-in MCP server lets compatible AI clients add job applications and Question Bank entries with user approval, and save a job-match analysis when the required resume and job-description conditions are met. AI features can run locally through Ollama or through several cloud model providers.
Tools
The tool list has not been reviewed yet.
Setup
Sign in to JobSync, open Settings > MCP Access, generate an access token, and copy the configuration snippet. Claude Desktop requires mcp-remote; add the configuration to mcpServers in claude_desktop_config.json and fully restart the client. Clients with native streamable-http support can connect directly to /api/mcp using an Authorization Bearer token. For a plain HTTP LAN address, mcp-remote may require the --allow-http argument.
claude_desktop_config.json
{"mcpServers":{"jobsync":{"command":"npx","args":["mcp-remote","http://<your-jobsync-url>/api/mcp","--header","Authorization: Bearer <your-token>"]}}}
Fit and risk
Not for
- Users expecting the MCP server to provide full job search, task, or activity-management capabilities; the README does not document those MCP capabilities.
- Users unwilling to grant an AI client permission to write job applications or Question Bank entries.
- Users seeking a hosted third-party integration without deploying JobSync themselves.
Required permissions
- Access to the self-hosted JobSync /api/mcp endpoint.
- A Bearer access token generated under Settings > MCP Access.
- With user approval, the ability to add job applications and Question Bank entries and resolve or create related companies, titles, locations, and tags.
- When a default resume and sufficiently substantial job description are available, the ability to save a job-match result based on that resume.
Risks and side effects
- The access token is shown only once; exposure could allow others to access the MCP endpoint.
- AI-generated matching scores, recommendations, and written content require human review.
- Job-posting text is treated as untrusted input, but users should still inspect confirmation-card details before saving.
- Cloud AI providers introduce different privacy considerations from running models locally with Ollama.
Troubleshooting
- Verify that JobSync is running and that the /api/mcp URL is reachable from the client.
- Verify that the Bearer token is complete, unexpired, and placed in the Authorization header.
- Claude Desktop must use mcp-remote and be fully quit and restarted after configuration changes.
- Add --allow-http when required for a non-HTTPS LAN URL.
- Confirm that JobSync has a selected AI model supporting structured output and tool calling.
Use cases
Add job applications from chat while resolving or creating companies, titles, locations, and tags.
Record interview questions and answers in the Question Bank from chat.
Save a job-match score, recommendation, and analysis when a substantial job description and default resume are available.
Supported clients
Claude DesktopPartial support
OpenClawFull support
HermesFull support