ISO 27001 MCP server: running an ISMS with an AI assistant

What is an ISO 27001 MCP server?

MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant such as Claude or Copilot use another program: it reads data there and calls functions. An ISO 27001 MCP server is the MCP server of a tool in which a company runs its ISMS, its information security management system.

There are two kinds. A knowledge server answers questions about the standard and does not know your company. The server of your own tool reads your records and, depending on the vendor, writes to them too. Only the second kind takes work off your hands in your own lists.

The nisd2.eu MCP server is of the second kind. It works in the NIS 2 walkthrough, which does not run an ISO 27001 ISMS.

What can an AI assistant keep up in an ISMS?

ISO 27001 is paywalled. We give the standard's numbers, titles and content here as the nisd2.eu data model records them. The measures in the standard's Annex A are called controls there.

An assistant mostly keeps up lists whose facts already exist somewhere else. It compiles the inventory of information and other associated assets (control A.5.9) from an existing inventory list and your invoices. It reads the suppliers, and what their contracts settle on security (A.5.19 and A.5.20), from your accounts payable list and the contracts.

In the risk register (clauses 8.2 and 8.3) it proposes for each entry how often damage can occur and how large it would be. It drafts policies and a first version of the Statement of Applicability, which our data model places under risk treatment.

All of these are drafts. An assistant knows your company from what it may read and what you tell it. Whether an entry is right is checked by someone who knows the business.

What the standard leaves to management and risk owners

According to our data model, top management reviews the ISMS at planned intervals, looking at audit results, metrics, incidents and changes (management review, clause 9.3). Under clause 5.1 it approves the policy and provides the resources.

Under clause 6.1.3 the risk owners, the people accountable for a risk, approve the risk treatment plan and accept the residual risks.

NIS 2 starts with management: the management bodies approve the measures and oversee their implementation (Art. 20(1) NIS 2). For certain digital services, such as cloud and data centres, Implementing Regulation (EU) 2024/2690 is more specific. There the management bodies accept the risk assessment results and the residual risks, or accountable persons with the authority to manage risks who report to management (Annex point 2.1.1).

An assistant can gather the material for the management review. Reviewing, accepting and approving stay with the people the standard and the law name for it.

ISO/IEC 27001:2022 clauses 5.1, 6.1.3, 9.3 · Art. 20(1) NIS 2

Who issues the ISO 27001 certificate?

A certification body, after an audit. In Germany the Deutsche Akkreditierungsstelle (DAkkS) accredits such bodies; it describes itself as the national accreditation body. A DAkkS accreditation annex for one certification body names ISO/IEC 17021-1 and ISO/IEC 27006-1 as the yardstick. The second sets the requirements for bodies that audit and certify information security management systems.

The database of accredited bodies on dakks.de shows whether a body is accredited for ISO 27001. Neither an assistant nor a tool replaces the audit, nisd2.eu included: it takes you through your NIS 2 obligations.

Where the NIS 2 walkthrough and ISO 27001 overlap

In a table (version 1.2 of 21 August 2025), ENISA, the EU's cybersecurity agency, maps each point in the Annex to Implementing Regulation (EU) 2024/2690 to parts of ISO 27001:2022. The asset inventory (Annex point 12.4) to A.5.9, for example, the risk management framework (point 2.1) to 6.1.3, 8.2 and 8.3 among others, and the effectiveness of measures (point 7.1) to 9.3 among others.

On its cover page ENISA writes that the table “should not be interpreted as a measure of equivalency among different standards or frameworks”. It names relevant requirements “without assessing whether these fully cover the requirements of the regulation”.

Our mapping in the nisd2.eu data model sets the walkthrough items beside them: 2.2 to A.5.9, 2.3 to 8.2 and 8.3, 5.2 to A.5.20, 6.3 to A.8.8, 4.4 to A.8.13 and 7.3 to 9.3. It is our reading, not a statement by any certification body. For an ISO 27001 project these lists are a start.

ENISA mapping table v1.2 · Annex CIR 2024/2690