Skillmatch MCP Server

Connect Skillmatch to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Job search and ranking pipeline via MCP for Claude Desktop. The skillmatch mcp server is what makes that connection.

What the server does

Claude-powered job fit analyzer for people who prove their skills through work, not credentials.

• Analyze how well you fit a specific job description based on your actual projects and resume
• Build optimized job search queries tailored to your targets and constraints
• Track every application you submit in a local SQLite database
• Pull your public GitHub repos to highlight relevant work during fit analysis

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Field — Type
• work_style — object
• optimizing_for — array
• unlisted_skills — array
• developing_skills — array
• dealbreaker_detail — array
• rejection_patterns — array
• Key — Required
• gmail_user — yes
• gmail_app_password — yes
• email_to — no
• email_cap — no

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Skillmatch's toolset — Field, work_style, optimizing_for and 9 more — is a fair guide to whether it matches your workflow. It is maintained by jarmstrong158; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Skillmatch's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Skillmatch.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.