Connect Brreg to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Brreg Norway Company Register, install it with no key, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Brreg Norway Company Register + Microsoft Copilot

Norwegian company register open data from the Brønnøysund Register Centre, no API key: search and read legal entities and their establishments, roles (CEO, board, auditor), corporate group structure, change feeds, and filed annual accounts with key figures and PDF copies.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

(none: public data, no API key)

Step 1 — Set up the connector

Public data, no key: setup takes under a minute. The connector reads the open data APIs of the Brønnøysund Register Centre (Brønnøysundregistrene): the Central Coordinating Register for Legal Entities (Enhetsregisteret: every Norwegian company, sole proprietorship, association and public body, with roles and group structure) and the Register of Company Accounts (Regnskapsregisteret: key figures and copies of filed annual accounts). No account, API key or sign-in is needed.

1. In the connector store, pick Brreg Norway Company Register and install it. There is nothing to paste and no Authorize with Provider step.
2. Check it with brreg_get_entity and the organisation number 923609016 (Equinor ASA): it returns the company's name, legal form, addresses, NACE codes and employees.

Cloud and self-hosted work the same way: there is nothing to configure in either.

Identifiers: the organisation number (organisasjonsnummer) has 9 digits, for example 923609016. The VAT number is the same digits with MVA appended (NO 923 609 016 MVA). A main entity (enhet) is the legal person; a sub-entity (underenhet) is an establishment with its own 9-digit number that belongs to a main entity.

Where to start: brreg_search_entities finds companies by name (set name_search_method to FORTLOEPENDE for an exact phrase) or by filters such as organisation form, NACE code, municipality, employees, bankruptcy or liquidation. brreg_get_entity returns the full record. For people and control, brreg_get_entity_roles lists the CEO, board and auditor, brreg_get_group_structure shows the parent and subsidiaries, and brreg_get_roles_in_other_entities lists the board seats and stakes the company holds elsewhere. Establishments come from brreg_search_sub_entities (with parent_organisation_number) or brreg_get_sub_entity.

Finances: brreg_get_annual_accounts returns the key figures of the last three filed years: operating revenue, operating result, result before tax, net result, assets, equity and debt, for the company (SELSKAP) or the group (KONSERN). For older years or the full document with notes, board report and auditor report, brreg_list_annual_report_copy_years lists the years and brreg_get_annual_report_copy attaches the PDF.

Monitoring: brreg_list_entity_updates, brreg_list_sub_entity_updates and brreg_list_role_updates return change feeds since a timestamp (ISO 8601, for example 2026-11-01T00:00:00.000Z) or an update id. Each event says whether the entity is new, changed, deleted or removed.

Reading the data: field names are Norwegian, and the AI translates them: navn name, organisasjonsform legal form, forretningsadresse business address, naeringskode1 main NACE code, antallAnsatte employees, konkurs bankrupt, underAvvikling in liquidation, registrertIMvaregisteret VAT registered. Role codes include DAGL (CEO), LEDE (chair), MEDL (board member), VARA (deputy) and REVI (auditor). brreg_list_organisation_forms and brreg_list_municipalities decode legal forms and 4-digit municipality numbers.

Personal data: roles name private persons with their birth dates. Use them for business purposes such as due diligence or KYC only.

Read-only: every tool only reads, so there is nothing to confirm and no tool is switched off at install.

Limits: searches page from page 0, and page times size must stay under 10,000; narrow the filters to go deeper. The open accounts service holds only the last three years of key figures (older years answer 404; use the PDF copies). Annual report PDFs over 10 MB are not attached. Brreg publishes no fixed rate limit but blocks abusive traffic; for whole-register analysis use its bulk downloads instead of paging.

Licence: the data is published under the Norwegian Licence for Open Government Data (NLOD) 2.0. Credit the Brønnøysund Register Centre as the source when you republish it.

The connector does not register or change anything in the Brønnøysund registers.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Brreg Norway Company Register tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Look up organisation number 923609016 and give me the legal form, business address, NACE code and number of employees."
• "Who is the CEO, the chair and the auditor of Equinor ASA?"
• "Show the key figures of the last three annual accounts for 923609016: revenue, operating result, net result and equity."
• "Find active Norwegian companies in Oslo with at least 50 employees and NACE code 62.010."
• "Which entities in our supplier list changed since 1 November 2026, and what kind of change was it?"

FAQ

Can it read accounts older than three years? Not as key figures: the open accounts service holds the last three filed years. For earlier years, brreg_list_annual_report_copy_years shows which PDF copies exist and brreg_get_annual_report_copy attaches them.

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude