Autario MCP vs Apiverket MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Autario MCP vs Apiverket MCP
In-depth architectural comparison of the Autario MCP and Apiverket MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Autario MCP
Data Platforms · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Apiverket MCP
Data Platforms · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose Autario MCP if you need specialized Data Platforms tools running via a local process. Choose Apiverket MCP if your workspace requires Data Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Autario MCP when:
You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Search, query, and publish charts across 2,300+ verified public datasets (World Bank, IMF, Eurostat, OECD, WHO). 28 MCP tools for data discovery, analysis, and visualization. Remote MCP + npm package.
Query Swedish public data through Apiverket, including company data, SCB statistics, weather, transport, and more. Install: npx -y apiverket-mcp-server.
Category & Scope
Tools & Capabilities Breakdown
Autario MCP Tools (28)
search_datasets
Search the Autario public data catalog. Returns dataset IDs, titles, descriptions, categories, publishers, row counts, last_refreshed_at, AND trusted ontology fields (topic, subtopic, unit, frequen...
list_indicators
Browse the Autario indicator registry — semantic layer over all 2600+ datasets. Each indicator has a topic (economy, health, energy, …), unit (USD, %, years, …), frequency (year/month/day), and ent...
get_entity_profile
Get all indicators available for one entity (country, aggregate, etc.). Returns indicator IDs with metadata + time coverage. Use this to discover what you can query about Germany, USA, G7, or any k...
get_dataset_info
Get full metadata for a specific dataset including title, description, publisher, category, keywords, row count, and creation date.
get_dataset_schema
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Autario MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, Apiverket MCP belongs to Data Platforms using local stdio subprocess. Select Autario MCP when you need capabilities focused on data platforms and Apiverket MCP when you require tools for data platforms.
Get the column names, data types, and total row count for a dataset. Always call this before query_dataset to understand the available columns for filtering and sorting.
query_dataset
Query data from a dataset with optional filtering, sorting, and field selection. Supports server-side aggregations (avg/sum/count/min/max/stddev/median) with optional GROUP BY for token-efficient q...
list_charts
List published chart visualizations on Autario. Returns chart IDs, titles, insights, linked datasets, and creation dates. Use to discover existing analyses.
get_chart
Get a specific chart by ID or slug. Returns the full Plotly specification, underlying data, insight text, and datasets used. The chart URL is shareable at autario.com/chart/{id}.
get_entity_data
Fetch wide-format data for ONE entity across MULTIPLE indicators — joined automatically on time via shadow columns. This is the "cross-dataset join" capability: no manual relationship setup needed....
compare_entities
Compare ONE indicator across MULTIPLE entities (e.g. GDP of DEU vs USA vs CHN). Returns wide-format rows like [{time:"2020", DEU:3846, USA:20937, CHN:14688}, …]. Use this for country comparisons, c...
verify_value
Verify that a claimed value is correct. Use this when a user asks "did you hallucinate that?" or when you want to double-check your cited numbers before presenting. Pass the indicator, entity, time...
describe
Summary statistics for a single indicator+entity: n, mean, median, std, min/max, quartiles, skew, histogram. Use FIRST before running any test so you know what the data looks like (sample size, com...
+16 more tools listed on main page
Apiverket MCP Tools (2)
govdata_discover
Search and browse available Swedish government data endpoints in the Apiverket API.
Use this tool to find the right endpoint before calling govdata_query. The API covers 139 endpoints across 16 categories including weather, transport, economy, health, environment, parliament, police, education, and more.
Args:
- query (string, optional): Keyword to search across endpoint names, descriptions, and paths
- category (string, optional): Filter by category name
When called with no arguments, returns all available categories with endpoint counts.
Examples:
- Find weather endpoints: query="weather"
- Browse transport category: category="Transport"
- Find pension info: query="pension"
- List all categories: (no arguments)
Returns:
Matching endpoints with their paths, parameters, and descriptions.
govdata_query
Call any Apiverket API endpoint to retrieve Swedish government data.
Use govdata_discover first to find the right endpoint path and required parameters. Then call this tool with the endpoint path and any path/query parameters.
Args:
- endpoint (string, required): The API path (e.g. "/v1/weather/{city}")
- path_params (object, optional): Values for path parameters like {city}, {code}, {id}
- query_params (object, optional): Query string parameters (q, limit, offset, lat, lon, etc.)
Examples:
- Current weather in Stockholm:
endpoint="/v1/weather/{city}", path_params={"city": "stockholm"}
- Search jobs:
endpoint="/v1/jobs/search", query_params={"q": "developer", "limit": 5}
- Train departures from Stockholm Central:
endpoint="/v1/transport/trains/{station}", path_params={"station": "Cst"}
- Exchange rates:
endpoint="/v1/rates"
- Population by municipality:
endpoint="/v1/population/{municipalityCode}", path_params={"municipalityCode": "0180"}
- Police events in Stockholm:
endpoint="/v1/police/events", query_params={"location": "Stockholm", "limit": 10}
- Find EV chargers near a location:
endpoint="/v1/infrastructure/ev-chargers", query_params={"lat": 59.33, "lon": 18.07}
Returns:
The API response as JSON, containing a "meta" envelope with request info and a "data" object with the actual data.
Error handling:
- Returns clear error messages if the API is unreachable, the endpoint doesn't exist, or parameters are invalid
- Large responses are automatically truncated with pagination guidance