Arbetsförmedlingen MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Arbetsförmedlingen MCP Visa mig jobb som systemutvecklare i Göteborg"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Arbetsförmedlingen MCP
An MCP server for the open APIs of Arbetsförmedlingen (the Swedish Public Employment Service, JobTech). It lets an AI assistant search Platsbanken job ads, read full ad texts, get labour-market statistics and look up taxonomy codes - using plain words, no API keys.
🚀 Features
Job search: free text, locations, occupations, skills, employment type, remote work, traineeships, radius around coordinates.
Names instead of codes:
"Göteborg","Systemutvecklare","Python"are automatically mapped to taxonomy concept ids (you can also pass the ids directly).Full job ad: description, requirements, conditions, contacts, application link.
Statistics: number of ads by region, municipality, occupation, skill.
Autocomplete and taxonomy: suggestions like in Platsbanken and lookup of official names.
Compact responses: only the needed fields, so the model context isn't filled with raw JSON.
No keys or registration: uses the open JobSearch and Taxonomy APIs.
Related MCP server: mcp-riksdagen-se
📂 Project structure
.
├── README.md
├── package.json
├── src/
│ ├── index.js # Entry point (stdio transport)
│ ├── server.js # MCP tool definitions
│ ├── api.js # JobSearch and Taxonomy client, taxonomy cache
│ └── format.js # Ad and statistics compaction
└── test/
└── format.test.js📦 Installation
cd arbetsformedlingen-mcp
npm installRequires Node.js 20+.
🔌 Connecting
Claude Code
claude mcp add arbetsformedlingen -- node /path/to/arbetsformedlingen-mcp/src/index.jsClaude Desktop / Codex / any MCP client
{
"mcpServers": {
"arbetsformedlingen": {
"command": "node",
"args": ["/path/to/arbetsformedlingen-mcp/src/index.js"]
}
}
}Debugging with MCP Inspector
npm run inspectEnvironment variables (optional)
Variable | Default | Purpose |
|
| JobSearch API address |
|
| Taxonomy API address |
|
| Request timeout |
🛠 Tools
All tools are read-only.
search_jobs - job search
Parameter | Description |
| Free text (job title, technology, employer) |
| Locations: names or concept ids |
| Occupations and occupational fields |
| Skills |
| Employment type, extent (Heltid/Deltid), workplace model |
| Employer name or organization number |
| Flags: remote work, traineeship, apprenticeship, "open to all" |
| Only ads with no experience requirement |
| Whether a driving licence is required |
| Publication period |
| Radius search |
| Pagination ( |
|
|
| How many characters of the description to include in the card |
get_job - job ad by ID
Full description, requirements (must_have / nice_to_have), salary, address, contacts and how to apply. Parameter: id.
job_stats - statistics
Accepts the same filters as search_jobs, plus group_by (region, municipality, occupation-name, occupation-group, occupation-field, country, employment-type, worktime-extent, skill, language) and top.
suggest - autocomplete
Suggestions by word prefix: q, limit.
search_taxonomy - taxonomy lookup
Finds concept ids and official names: type, query, limit. Rarely needed - search_jobs maps names itself - but handy for ambiguous cases.
⚠️ Limitations
Data comes from public APIs in real time; an internet connection is required.
JobSearch itself caps a request at 100 ads and offset at 2000, so one search yields at most 2100 ads - refine filters (e.g. by date) for larger result sets.
The
remote,traineeandlarlingfilters rely on analysis of ad texts and may be inaccurate.Ad texts are mostly in Swedish.
🧪 Tech stack
Node.js ESM, no build step
@modelcontextprotocol/sdkandzodfor tool schemasJobSearch API and Taxonomy API from JobTech
Tests:
npm test(node --test)
Available Tools
5 toolsget_jobJob by IDARead-onlyIdempotent
Full ad details: description, requirements, conditions, contacts and how to apply. The ID comes from search_jobs.
Inputs: id (required).
job_statsJob statisticsARead-onlyIdempotent
Number of jobs broken down by region, municipality, occupation, field, skill, etc. For example: "how many Python jobs per region". Accepts the same filters as search_jobs.
Inputs: q, top, skill, region, +19 more.
search_jobsSearch jobsARead-onlyIdempotent
Search jobs in Platsbanken (Arbetsförmedlingen). All filters are optional and combined with AND. Places, occupations and skills can be given as plain names — they are matched to the taxonomy automatically. Returns short cards; use get_job for the full ad text.
Inputs: q, sort, limit, skill, +21 more.
search_taxonomyJobTech taxonomy searchARead-onlyIdempotent
Finds concept ids and official names for occupations, municipalities, regions, skills, languages, etc. Usually only needed when a name is ambiguous: search_jobs matches names itself.
Inputs: type (required), limit, query.
suggestQuery autocompleteARead-onlyIdempotent
Free-text suggestions (skills, occupations, places, employers) from the start of a word — as in Platsbanken.
Inputs: q (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct layer: search_jobs for ads, get_job for a single ad's detail, job_stats for aggregates, search_taxonomy for concept IDs, and suggest for autocomplete. The only soft overlap is search_taxonomy vs suggest, since both resolve names to taxonomy concepts, but the descriptions clearly frame one as a lookup/ID resolver and the other as start-of-word autocomplete.
All names are lowercase snake_case, which is consistent at the style level. The verb pattern is mostly verb_noun (search_jobs, search_taxonomy, get_job), with minor deviations: job_stats is noun-only and suggest is a bare verb without an object, though both remain unambiguous.
Five tools is tightly scoped to a job-search domain: search, detail, statistics, taxonomy lookup, and autocomplete. Nothing feels redundant and there is no obvious operation left out that would need its own tool.
The surface covers the full read path of a job board: discovery via search_jobs, drill-down via get_job, aggregation via job_stats, plus taxonomy resolution and autocomplete. Minor gaps exist—no bulk taxonomy enumeration or employer/application lookup—but agents can work around these using search_taxonomy and suggest.
Related MCP Connectors
Search open jobs in Sweden from your AI assistant, with full listings and apply links.
The career management plugin for your own AI assistant: CVs, cover letters, interviews and more.
Jobs, ads, SEO, keywords, YouTube and AliExpress data for AI agents. Runs on Apify.
LinkedIn jobs, companies and people for AI agents, plus messages and invites via your own account.
Related MCP Servers
- AlicenseAqualityDmaintenanceQuery Swedish public data from AI tools. Includes company data, SCB statistics, weather, transport, public agencies, and more through the Apiverket API.253 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query Swedish Parliament open data through natural language.95 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to search job listings and retrieve job details, as well as view and manage career-profile information such as work history, job summaries, career aspirations, and technical skills.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to search and retrieve job listings, and to read or manage career profile data such as work history, job summaries, career goals, and technical skills.-