Claude Code · Setup

How do I add the NIS2 walkthrough to Claude Code as an MCP server?

The command claude mcp add puts the walkthrough into Claude Code as an MCP server. Then you type /mcp, sign in through the browser and allow access. From then on Claude Code reads your items in the NIS 2 walkthrough and fills in what they ask for; finishing and signing stay in the app.

Inizia ora
Simon OrzelCory Hisey

Prenota una chiamata

Simon OrzelSimon Orzel·

How do I connect Claude Code with a browser sign-in?

MCP (Model Context Protocol) is the protocol an AI assistant uses to talk to other software. Beforehand, an admin has turned on "Allow AI assistants for this company" in Settings, and your account has access to the walkthrough.

The command below adds the server to Claude Code, with the address https://nisd2.eu/api/mcp. Then start Claude Code, type /mcp and follow the steps in your browser.

After you sign in, the nisd2.eu page shows which assistant asks for which company and where the browser returns to. For Claude Code that is localhost with a port number: your own computer, where Claude Code receives the answer.

Click "Allow". If your last sign-in was more than 15 minutes ago, you sign in again first. The reason: an assistant stays connected even after you sign out of the browser.

claude mcp add --transport http nisd2 https://nisd2.eu/api/mcp

How do I connect Claude Code with a key?

For scripts, or a computer without a browser, click "Create key" in Settings. The key is shown only at that moment. It lasts 90 days, in the company that was open when you made it.

Put it in the environment variable NISD2_MCP_KEY and add the server with the command below. The shell fills in the value when you run it, so your history holds only the variable's name.

Unless you say otherwise, Claude Code stores the server and its key in the file ~/.claude.json in your home folder. Do not use the project scope: it writes to .mcp.json in the project, a file Anthropic intends to be checked into the repository.

claude mcp add --transport http nisd2 https://nisd2.eu/api/mcp --header "Authorization: Bearer $NISD2_MCP_KEY"

Does Claude Code reach an instance inside the company network?

Yes. Claude Code runs on your computer and connects from there, so it also reaches a self-hosted instance inside the company network. Put that instance's address in the commands instead of nisd2.eu.

Claude on the web and desktop, by contrast, connects from Anthropic's cloud, according to Anthropic. For that the instance has to be reachable from the internet.

What do I give Claude Code as a first task?

A file from your own records and an item. For 5.1 the list of creditors from your accounting fits, since almost everyone who works for you sends you invoices. An example request is below.

To fill an item in, Claude Code needs the item with its fields and the rows already on the list. The tool get_walkthrough returns both.

In "Manual" mode, according to Anthropic, Claude Code asks for permission the first time it uses each tool. Under /permissions the rule mcp__nisd2__get_walkthrough allows reading for good. Let filling in keep asking, so you confirm each change yourself.

We tested Claude Code on a local instance, with the browser sign-in and with a key. In the test on 14.10.2026 it read the walkthrough, filled in four items, left the rest open and signed nothing.

Read item 5.1 of the NIS 2 walkthrough and add the suppliers from creditors.csv. Leave empty whatever the file does not show.

What stays with me afterwards?

Every screen Claude Code wrote carries a mark such as "Filled in by the assistant claude-code/2.1.287 on 16 October 2026". The activity log shows each change under your name, "via" the assistant's name.

Finishing, deciding an item is not applicable and signing exist only in the app. No tool of an assistant can finish or sign an item.

The walkthrough is built on that. Under Art. 20(1) NIS 2 the management body, in a GmbH its managing directors, approves the measures and oversees their implementation. In Germany, § 38(1) BSIG obliges management to implement them and oversee their implementation.

Art. 20(1) NIS 2 · § 38(1) BSIG

How the walkthrough does it

Good first items are those whose answers already sit in your files.

2.2 "Write down what your company has": from an inventory list or a licence overview, Claude Code ticks software and devices and enters on "Which software exactly, and from whom?" who provides them.

5.1 "Write down who works for you": the providers from 2.2 are already there. From the list of creditors, Claude Code adds the others, one line each with what they do for you.

4.4 "Record your backups": for each backup system on your list, Claude Code enters how often it backs up and when a restore from it last worked. If none has worked yet, the field stays empty.

Then you open each item in the app, check the marked screens and finish it.

Common questions

Can Claude Code upload files over MCP?

It is built for that, since Claude Code can send a file's bytes itself. The tool upload_file gives an address to upload to, then Claude Code attaches the file to the item, as evidence or as the certificate of a training. A file counts as evidence only once it is stored at its full size. We have not yet tested uploading with Claude Code itself.

Do I have to explain to Claude Code what NIS 2 requires?

No. For each item, get_walkthrough returns the walkthrough's own words, its fields with their schema and what is already entered. The server also gives every assistant instructions, such as entering only what your records show and leaving a field out when in doubt.

I belong to several companies. Which one does Claude Code work for?

The company that was open in the app when you allowed it or created the key. For another company, switch company in the app and connect again.

Does Claude Code stay connected when I sign out?

Yes. You disconnect in Settings under "Connected": one at a time with "Disconnect", or all at once with "Disconnect all assistants". Changing your password also disconnects every assistant.

How many MCP calls are allowed per hour?

300 tool calls per person per hour, for all of that person's assistants together. Beyond that the server answers that there were too many calls in the last hour. The next hourly window starts fresh.

Read next

Sources

  • Anthropic, Claude Code documentation on MCP, code.claude.com/docs/en/mcp
  • Anthropic, Claude Code documentation on permissions, code.claude.com/docs/en/permissions
  • Directive (EU) 2022/2555 (NIS 2), Art. 20(1), EUR-Lex
  • BSIG, § 38(1), gesetze-im-internet.de
  • open-isms, lib/mcp/server.ts, lib/mcp/key.ts and lib/mcp/oauth.ts, github.com/NISD2/open-isms

In pratica

Dove compare nel percorso guidato

Il percorso guidato ne fa dei passi da compilare, con la legge spiegata accanto a ciascuno. Apri un passo per vedere la sua schermata, compilata per un'azienda di fantasia.

Il percorso è in tedesco e in inglese.

  1. Risk Management

    Write down what your company has

    A list of the processes, software and devices you work with.

  2. Supply Chain Security

    Write down who works for you

    A list of your suppliers and service providers.

  3. Business Continuity

    Record your backups

    How often you back up, and when a restore last worked.

Quanto costa il percorso guidato

Percorso guidato NIS 2
Implementazione guidata su nisd2.eu.

4800 € netti all'anno, più IVA

Rimborso entro 30 giorni

Con fattura, da pagare entro 30 giorni. Annullamento entro i primi 30 giorni: fattura annullata o rimborso.

Implementazione guidata della NIS 2, passo dopo passo

Una cronologia di modifiche e approvazioni da mostrare alla tua autorità di vigilanza

Scadenze e promemoria per ogni requisito

Questionario di sicurezza per i tuoi fornitori

Esportazione in PDF o CSV in qualsiasi momento

Prezzi e condizioni

Ti hanno affidato NIS2?

Ti guidiamo passo dopo passo. Tu compili, noi spieghiamo ogni punto con parole semplici, e alla fine firma la direzione.

Inizia ora
Simon OrzelCory Hisey

Prenota una chiamata

Prezzi e condizioni
Il percorso NIS2: la tua strada passo dopo passo, i primi punti completati