Integration

cvr.dev integration

cvr.dev is an independent API over the Danish Central Business Register (CVR), refreshed every minute. Look up a Danish company by CVR number or name (name, legal form, status, founding date, industries, employment, address area), find production units by P-number or address, list a company's published annual reports with links to their PDF and XBRL files, follow ownership up (owners with their share and voting rights) and down (subsidiaries), read employee and full-time-equivalent history, and search companies by industry, legal form, postal code, municipality, founding date and size. To protect people, the register's participant data is not returned: no roles (directors, board, founders), no owner names (a person owner appears only as type PERSON with its unit number), no names in annual report approvals, no street addresses and no phone numbers or emails, since a sole proprietorship (ENK) is a person. Companies marked reklamebeskyttet must not be contacted for sales (Danish law). Plans: Starter (99 DKK/month, 1250 requests/month, 3 per second) covers company, production unit and annual report lookups only; Business and Business Pro add ownership, search and employees. Authentication is a cvr.dev API key sent as Authorization: Bearer <key>.

Connect cvr.dev How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in cvr.dev.Built from the 8 cvr.dev tools below, on the connection you add once.

What you can do with cvr.dev

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Company, 2 operations

get_companyGet companyGETLooks up Danish companies by CVR number or by name (cvr_nummer wins when both are given). Returns a list (several on a name search) with name, legal form, status, industries, employment and address area.
search_companiesSearch companiesGETSearches Danish companies matching every filter given (industry codes, legal forms, postal codes, municipalities, founding dates, employees, full-time equivalents), up to 100 per call. Business plan; can be slow.

Annual report, 1 operation

list_annual_reportsList annual reportsGETLists a Danish company's published annual reports with their accounting period, publication time and links to the PDF and XBRL files. Only the active (not revised) report per period unless omgjort=true.

Api key, 1 operation

test_api_keyTest api keyGETChecks that the API key is valid and returns the cvr.dev user id it belongs to. Does not count toward the monthly request quota.

Company owner, 1 operation

list_company_ownersList company ownersGETLists the direct and indirect owners of a Danish company with ownership share and voting rights. Owner names are withheld: a company owner has a CVR number (use get_company), a person shows as type PERSON. Business plan.

Employee count, 1 operation

get_employee_historyGet employee historyGETReturns a Danish company's history of employee and full-time-equivalent counts (monthly since late 2019, quarterly or yearly before). Business plan.

Production unit, 1 operation

get_production_unitsGet production unitsGETLooks up Danish production units (a company's physical sites, P-numbers) by P-number or by address (p_nummer wins when both are given). Returns name, owning company CVR number, status, industries and area.

Subsidiary, 1 operation

list_subsidiariesList subsidiariesGETLists the subsidiaries of a Danish company, the whole hierarchy below it, with ownership share, voting rights and distance. Business plan.

Use cvr.dev from Claude Code, Cursor or Codex

Connect cvr.dev in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its cvr.dev operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect cvr.dev

Create your workspace
Sign up free. Nothing to install.
Connect cvr.dev once
Add your cvr.dev connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.