Domera MCP Server
Official# Domera MCP server
Free, read-only MCP server that tells an AI assistant which inspections a **Swedish residential or commercial building** must or should have, how often, on what legal basis, who may perform them, and (given last-done dates) what is overdue.
Covers: OVK ventilation inspection, energy declaration, lift inspection, radon, legionella and fire-safety follow-up. Answers in English, Swedish or Spanish. No account, no API key, nothing stored.
Built by [Domera](https://domera.se), property management and bookkeeping software for Swedish landlords and housing co-operatives (BRF).
## Use
Remote (Streamable HTTP): `https://mcp.domera.se/mcp`
Claude Desktop / any stdio client:
```json
{ "mcpServers": { "domera": { "command": "npx", "args": ["-y", "@domera/mcp-server"] } } }
```
## Tool
`swedish_building_obligations` with optional `ventilation` (`FT_FTX` | `F_FX_S`), `has_lift`, `language` and `last_done` (a date per obligation).
General information, not legal advice. Always check the current regulations.
## What this repository is
A thin client over a public endpoint (`/api/public/obligations`). It contains no Domera application code. MIT licensed.
## Contact
hej@domera.se · https://domera.se
TDQS
Scored across 1 tool
With only a single tool there is no possibility of misselection between tools; the purpose (list Swedish building inspection obligations with intervals, legal basis, and status) is unambiguous. An agent will always know when to call it.
The single name is snake_case and descriptive, following a noun-oriented convention rather than a verb_noun pattern. Consistency cannot really be assessed with one tool, but the name is readable and domain-specific.
One tool is thin for a server that also computes status from last-done dates and covers many inspection types; a detail lookup or per-inspection query would round it out. It is borderline rather than wrong, since the domain is narrow.
The tool covers the core ask (obligations, intervals, legal basis, performer, status), but there is no way to fetch details for a single obligation, list obligations by property type explicitly, or get guidance beyond a flat list. Usable for a first pass, with notable gaps for deeper workflows.