Sweden MCP Servers 🇸🇪

A curated catalog of Model Context Protocol servers for Swedish data, laws and services. Written in English.

Explore the catalog · JSON API · Suggest a server · Contribute

The Model Context Protocol (MCP) connects AI assistants to external tools and sources through a standard interface. This repository is a catalog, not an MCP server implementation. It lists existing public projects with a specific connection to Swedish data or services, rather than ordinary APIs or generic integrations.

This is an independent community project, not an official Swedish government catalog. Inclusion is not an endorsement by this catalog, the data providers or the listed projects. Most listed integrations are community-maintained; consult their own documentation.

The catalog structure, JSON schemas, generators, contribution workflow and static site are adapted from France MCP Servers, itself based on Italia MCP Servers. The original MIT license and Copyright (c) 2026 Sab Severino are preserved in LICENSE. This is an independent repository and catalog, without their server entries or Git history.

1. Open the project's documentation and check its license, prerequisites and tools.
2. Check whether API keys, a local runtime or a paid account are required.
3. For a listed remote endpoint, use an MCP client supporting its documented transport.
4. Otherwise, review the source before following the project's installation instructions and configuring its launch command in your client.

A Connect link is an endpoint address, not a one-click installer or an uptime guarantee. Do not send secrets or personal data to an unfamiliar server. Tool output may be incomplete or untrusted; validate important weather, travel, legal or statistical information with the authoritative data provider.

Access and write cautions: Fortnox can create/bookkeep invoices; Bokio is read-only by default but can enable writes. Their account/API costs, and BolagsAPI pricing and quotas, have not been verified. ICA MCP uses an unofficial private API, requires login, can modify personal shopping lists, and may conflict with ICA's service terms. Runtime attempts deliberately stop before authentication or private account access; protocol discovery or a local ping does not prove an integration works with its provider. Consult the runtime outcomes and project-specific restrictions first.

Entries are checked against canonical public documentation and implementation sources. last_verified is the metadata consultation date, not proof that a server runs. The verification record explains source evidence, credentials, licensing and coverage limitations. The separate runtime smoke report records actual protocol/tool attempts, including failures and blocked paths. The 2026-09-14 runtime snapshot covers the 18 entries present before subsequent additions: 9 live-data passes, 5 credential blockers, 1 network/TLS blocker, 2 tool failures and 1 protocol failure. A pass covers only the sampled read-only operation and configuration. The curated-list additions were reviewed from source and documentation only: no runtime tests were attempted.

The 🎯 Ready score /100 measures documented readiness, not popularity, security or runtime reliability. Documentation assessments dated 2026-09-14 use the unchanged six-criterion rubric. A high score can coexist with a failed runtime attempt or missing credentials. Unassessed does not mean zero. Where assessed, scores link to the criteria and evidence; entries sort by descending score, then name, with unassessed entries last. Bold names, if present, are editorial selections, not certification.

• Metadata and star counts are dated snapshots, not continuously refreshed guarantees.
• Documented tool names may be a selection, not an exhaustive runtime inventory.
• No Ready scores are assigned for the current selection: metadata/source verification is separate from a complete six-criterion documentation assessment.
• The shared rubric v1 uses installation (30), configuration (20), tools (20), compatibility (15), license (10) and limitations (5). A future assessment must record original notes and canonical evidence for every criterion.
• The scheduled protocol checker sends only initialize. It does not certify tool behavior or availability. Manual tool-call evidence, if available, is recorded separately in VERIFICATION.md.
• Catalog code and original descriptions are MIT-licensed. Each external server and its upstream datasets have their own terms. license: null means no code license was verified; public source alone does not grant reuse rights.

servers/                 One source JSON file per listed server
schema/                  JSON Schema 2020-12 for entries and the published catalog
scripts/                 Validation, README/site generation, rubric and unit tests
scripts/templates/       Searchable static HTML catalog (no framework or backend)
.github/ISSUE_TEMPLATE/   Suggestion and correction forms
.github/workflows/        CI, scheduled link checks and GitHub Pages deployment
logo.svg                 Swedish blue/yellow catalog branding
VERIFICATION.md          Source evidence, runtime procedure and limitations

Only README blocks between BEGIN/END markers are generated. Narrative sections must be maintained separately. site/ is generated and ignored; do not commit it.

Use Python 3.12 or newer in a local virtual environment, then run:

python -m pip install -r scripts/requirements.txt
python scripts/validate_servers.py
python -m unittest discover -s scripts -p 'test_*.py'
python scripts/build_readme.py
python scripts/build_readme.py --check
python scripts/build_catalog.py
python -m http.server 8000 --directory site

Open http://localhost:8000/. The browser fetches catalog.json, so opening the HTML as a local file:// URL is not supported. See CONTRIBUTING.md for virtual-environment setup, deployment and the complete assessment checklist.

CI validates entries, unit tests, generated README synchronization and the site build. GitHub Pages builds and deploys from main; weekly/manual link checks separate ordinary web links from MCP protocol requests. Deployment and external checks can fail independently.

Contributions should document a genuine Sweden-relevant MCP implementation, its canonical sources and any access restrictions. Start with CONTRIBUTING.md.

The catalog is available under the MIT license. External projects, provider names and datasets remain subject to their respective licenses and terms.