How to Find and Use Swedish MCP Servers with Sweden MCP Servers

What Sweden MCP Servers provides

Sweden MCP Servers is a curated catalog of public Model Context Protocol (MCP) servers connected to Swedish data, laws, and services. MCP gives AI assistants a standard way to work with external tools and information sources.

The repository is a catalog, not an MCP server implementation. It does not provide one universal installation command or a single server endpoint. Instead, it helps you find separate projects, understand their requirements, and open each project's documentation before connecting it to an MCP-compatible client.

The catalog contains 26 servers across nine categories, including data and statistics, legal technology, government and public finance, public services, employment, transport, electronic invoicing, geospatial data, and other services.

Choose a project from the catalog

Start with the web catalog, where projects are grouped by category and described with their implementation language, available connection links, and other metadata.

• Statistics: Use projects connected to SCB, Kolada, or other statistical sources.
• Government and law: Explore parliamentary material, government documents, Swedish statutes, case law, and legal-position updates.
• Public services: Find education, weather, and public-data integrations.
• Transport: Review tools for SL journeys, departures, disruptions, road conditions, cameras, and traffic incidents.
• Business and finance: Inspect company, annual-report, accounting, invoicing, and bookkeeping integrations.

Do not treat the catalog's readiness information, star counts, or inclusion as a guarantee. The catalog explains that metadata dates are snapshots, documented tool names may not be exhaustive, and a documented connection does not prove that a server is currently available.

Inspect the machine-readable catalog

For scripts, dashboards, or your own discovery workflow, use the published JSON API. For example, retrieve the catalog from a shell:

curl -L https://bsab.github.io/sweden-mcp-servers/catalog.json

You can also load the same URL in an application that supports JSON. Use the project metadata to identify an entry, then follow its source repository and documentation for the actual setup instructions.

The catalog is useful for discovery and comparison. It is not a substitute for reading a project's license, prerequisites, authentication instructions, transport requirements, limitations, and current implementation details.

Set up a selected MCP server

Remote servers

Some entries include a hosted endpoint with a Connect link. An endpoint address is not a one-click installer and is not an uptime guarantee. Before using one, confirm that your MCP client supports the transport documented by the project.

1. Open the project's repository and read its current documentation.
2. Check whether the endpoint requires authentication, an account, an API key, or a paid plan.
3. Confirm that your MCP client supports the endpoint's documented transport.
4. Add the endpoint to your client using that client's documented remote-server workflow.
5. Test a read-only operation first and verify the returned information against the authoritative provider.

For example, the catalog lists hosted endpoints for projects such as MCP Sweden, Lantmäteriet MCP, Naturvårdsverket MCP, SMHI MCP, and Traktamente MCP. The presence of an endpoint does not mean that every tool has been tested or that provider access will succeed.

Local servers

Many entries are intended to run locally from source. In that case, follow the individual project's installation instructions rather than assuming that all projects use the same runtime or command.

1. Review the repository's prerequisites, such as Python, Node.js, TypeScript tooling, Go, or Bun.
2. Clone or download the project according to its documentation.
3. Install the dependencies using the project's documented process.
4. Configure required API keys, credentials, databases, or environment variables.
5. Register the project's documented launch command with your MCP client.
6. Start with a non-destructive tool call and inspect the result.

The catalog includes local projects written in Python, TypeScript, JavaScript, Go, and other documented environments. Their commands and configuration formats are project-specific, so copying a configuration from one entry to another may not work.

Basic usage examples

Ask for Swedish statistics

After connecting an appropriate statistics server, you might ask your AI assistant:

Find the relevant SCB table for population data, explain the available region and time selections, and return the values for the requested municipalities.

Projects such as SCB MCP and SCB Open Data MCP work with SCB PxWeb APIs, while Kolada projects focus on municipal and regional indicators. Check each project's documented tools and coverage before writing a prompt.

Search parliamentary information

With Riksdag & Regering MCP configured, a suitable request could be:

Search Swedish parliamentary documents for the specified topic, identify relevant debates or votes, and provide links to the underlying material.

Ask the assistant to preserve source references and distinguish retrieved documents from its own summary.

Check transport or weather information

For a transport or weather server, use a specific, read-only request:

Find the next departures from the specified Stockholm stop and identify any reported disruptions.

Or:

Return the latest documented forecast for the specified Swedish location and include the forecast time and source.

SL integrations, Swedish weather projects, SMHI integrations, and Trafikverket MCP differ in transport, data coverage, hosting, and authentication. Use the selected project's documentation to determine the exact tool names and parameters.

Evaluate access requirements and risks

Before connecting any entry, check the project's license, prerequisites, data provider, credentials, and limitations. The repository recommends reviewing both the verification record and the runtime smoke report.

• Credentials: Some projects require API keys, logins, approved access, or paid accounts.
• Runtime evidence: A protocol discovery request or local ping does not prove that the provider integration works.
• Data quality: Tool output may be incomplete or untrusted. Validate important legal, weather, travel, and statistical information with the authoritative provider.
• Privacy: Do not send secrets or personal data to an unfamiliar server.
• Licensing: Read the license and usage terms for both the MCP project and its underlying provider.

Be careful with write-enabled tools

Some catalog entries can change data or perform business actions. Fortnox MCP can create or bookkeep invoices. Bokio MCP is read-only by default but can enable writes. ICA MCP can modify personal shopping lists, uses an unofficial private API, requires login, and may conflict with ICA's service terms.

For these integrations, use a separate test account where possible, grant only the required permissions, and confirm every write operation before execution. The catalog's runtime attempts deliberately stop before authentication or private account access.

Use the repository's reports effectively

The runtime smoke report records protocol and tool attempts, including failures and blocked paths. A pass covers only the sampled read-only operation and configuration used in that test.

The verification record documents source evidence, credentials, licensing, and coverage limitations. It is especially useful when a server has no hosted endpoint or when the project requires a local database, provider approval, or a particular API key.

Keep these reports separate from your own testing. A project's status can change after the catalog's metadata consultation date, and the curated-list additions were reviewed from source and documentation without runtime tests.

Advanced tips for reliable workflows

• Prefer narrow prompts: Specify the location, date range, entity, or dataset you need instead of asking for an unrestricted search.
• Request provenance: Ask the assistant to identify the source, retrieval time, table, document, or provider used.
• Separate discovery from execution: First ask which tool and parameters will be used, then approve a read-only call.
• Validate high-impact results: Independently check information used for legal, financial, travel, employment, or public-safety decisions.
• Monitor credentials: Keep API keys outside prompts and source code, and follow the selected project's documented configuration method.
• Account for transport differences: The SL MCP Server, for example, documents legacy SSE transport rather than Streamable HTTP. Confirm compatibility before configuring it.
• Respect provider terms: An unofficial integration or private API may become unavailable or violate the provider's service terms.

Contribute or report corrections

If a relevant Swedish MCP project is missing, use the repository's new server form. To correct metadata or report a broken link, open the appropriate issue form.

Contributors should consult the repository's contribution guide. The catalog is an independent community project and is not an official Swedish government catalog. Inclusion does not constitute endorsement by the catalog, data providers, or listed projects.

Conclusion

Sweden MCP Servers gives you a practical starting point for discovering MCP integrations connected to Swedish information and services. Use the web catalog for browsing, the JSON API for automation, and each project's own documentation for installation and client configuration. Evaluate authentication, transport, runtime evidence, licensing, and write access before trusting a connection, and verify important results with the original data provider.