Connect BORME to Microsoft Copilot via MCP

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

BORME Spain Commercial Register Gazette + Microsoft Copilot

Spanish official gazettes from the BOE open data API, no API key: the daily BORME summary of the Commercial Register Gazette (company formations, appointments, capital changes, mergers, dissolutions, insolvencies, legal notices) with the text of each item, and the daily BOE summary with any BOE document.

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 of the Agencia Estatal Boletín Oficial del Estado (AEBOE): the BORME (Boletín Oficial del Registro Mercantil, the gazette of the Spanish Commercial Register, where every company formation, appointment, capital change, merger, dissolution and insolvency is published) and the BOE (Boletín Oficial del Estado: laws, regulations, appointments and public notices). No account, API key or sign-in is needed.

1. In the connector store, pick BORME Spain Commercial Register Gazette and install it. There is nothing to paste and no Authorize with Provider step.
2. Check it with borme_get_summary and the date of the last working day as YYYYMMDD: it returns that day's BORME summary.

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

Where to start: borme_get_summary returns a day's BORME. Section A has one item per province (MADRID, BARCELONA and so on); section C groups legal notices by type, such as general meeting calls, mergers, capital reductions and dissolutions, with one item per company. borme_get_item with an item identifier (for example BORME-A-2026-214-28 or BORME-C-2026-5833) returns its text. For laws and official notices, borme_get_boe_summary lists a day's BOE and borme_get_boe_item reads one document (for example BOE-A-2026-23341).

No search by company name: the BORME is organised by day and province. To find a company in section A, the AI reads the province item for that day and looks for the name. To follow a company over time, it reads the days in question, so tell it the date and province of the act when you know them.

Reading the data: section A acts include Constitución (formation, with purpose, registered office and capital), Nombramientos (appointments), Ceses/Dimisiones (removals and resignations), Ampliación and Reducción de capital, Cambio de domicilio social, Cambio de denominación social, Disolución, Extinción, Situación concursal (insolvency) and Fusión por absorción (merger). Roles include Adm. Unico (sole director), Consejero (board member), Apoderado (attorney) and Liquidador. Company forms are S.A., S.L., S.L.U./S.A.U. and S.COOP. The AI translates the Spanish terms.

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

Limits: dates are YYYYMMDD. Days without an issue (Sundays, most Saturdays for the BORME, holidays) answer 404. A province item of a big province such as Madrid or Barcelona can be long. The AEBOE publishes no rate limit; keep calls reasonable.

Terms of reuse: reuse is free under the AEBOE reuse conditions: cite the Agencia Estatal Boletín Oficial del Estado as the source, keep the meaning of the data, and mention the date of the publication. Only the PDF of the official gazette is authentic.

Common errors: 404 for a date means there was no issue that day: try the previous working day.

The connector does not publish anything in the BORME or the BOE and does not file with the Commercial Register.

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 BORME Spain Commercial Register Gazette 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

• "Summarise yesterday's BORME: how many company formations, dissolutions and insolvencies were published in Madrid?"
• "Read item BORME-A-2026-214-28 and list the new companies with their capital and registered office."
• "Which mergers and capital reductions were announced in section C of the BORME on 2026-11-06?"
• "Was there any appointment or resignation of directors for our supplier in the Barcelona BORME of 5 November?"
• "Show today's BOE summary and open the documents from the Ministry of Finance."

FAQ

Can it search the BORME for a company name across all dates? No. The BOE open data API organises the BORME by day and province, so the AI reads the days in question. Give it a date range and the province if you know 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