← All posts
Tutorial

NAPT MCP Server — Control Your Network From Claude

Your AI assistant, wired directly into your network automation platform.

NAPT Team7 min read
MCP: Claude to NAPT to devicesClaudeMCPNAPTdevices

The Model Context Protocol (MCP) lets an AI assistant call real tools. The NAPT MCP server exposes the platform — templates, script generation, intent parsing, dry-runs, pipelines, and findings — so you can drive your network from a chat window.

How it fits together

Your assistant talks to the NAPT MCP server, which talks to NAPT, which talks to your devices. Every call is scoped by your MCP key, so the assistant only ever sees what you can see.

Step 1 — Get a key

Open the MCP Keys panel and mint a key. Keep it read-only unless you actually plan to run scripts — execution permission is opt-in for a reason.

Step 2 — Add NAPT to your client

For Claude Desktop or Cursor, add the server to the MCP config:

json
{
  "mcpServers": {
    "napt": {
      "command": "npx",
      "args": ["-y", "@napt/mcp"],
      "env": { "NAPT_MCP_KEY": "napt_mcp_..." }
    }
  }
}

Step 3 — Test it

Restart your client and ask: "List NAPT templates for BGP." The assistant calls napt_search_templates and returns vetted scripts. From there you can generate, dry-run, and review findings without leaving the conversation.

Pro tip: Use a separate key per assistant so you can revoke one without breaking the others. Grant execute only on the key you use for change windows.
#mcp#ai#tutorial

Was this helpful?

Generate scripts for the task covered in this post

Describe what you need and NAPT writes production-ready automation in Netmiko, NAPALM, or Nornir.

Open Script Generator →
New to NAPT? Start with the Setup Guide

Related posts