Model Context Protocol

NAPT for your AI assistant

Connect Claude, Cursor, and any MCP-compatible client to NAPT. Generate scripts, parse change intent, run safe dry-runs, trigger pipelines, and triage findings — all from a natural-language conversation.

MCP Keys

Create, reveal, and rotate API keys. Scope permissions to generate, execute, read, and pipelines, and set expiry dates.

Best Practices

Prompt patterns that work, tool combinations, security guidance, limitations, and real example conversations.

Available tools

Your assistant can call these NAPT tools directly during a conversation.

napt_search_templates

Find vetted automation templates by intent or vendor

napt_get_script

Fetch the full source of any catalog script

napt_generate_script

Generate a tailored script from natural language

napt_parse_intent

Risk assessment and pre-flight checks for a change

napt_run_script

Execute a script — dry-run by default

napt_get_findings

Triage findings across your network domains

napt_get_pipeline_status

Inspect the latest pipeline runs

napt_trigger_pipeline

Kick off an async pipeline and poll its run_id

Get started

Connect NAPT to your AI assistant in three steps.

1Create an MCP key on the MCP Keys page and scope its permissions.
2Add NAPT to your MCP client config and reference the key via an environment variable.
3Restart your client and ask it to use NAPT.

Claude Desktop

Add the block below to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude.

json

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

Cursor

Add the block below to ~/.cursor/mcp.json (or Settings → MCP → Add new server), then reload Cursor.

json

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

Create your first key Browse the docs

Guided setup

Answer a few questions and we'll jump you straight to the fix if something isn't working.

Step 1 of 5

Have you created an MCP key and copied its value?

You need a key from the MCP Keys page, scoped to the tools you want to use.

Connection check

Tick each step to verify your Claude / Cursor MCP connection is set up correctly.

I created an MCP key and scoped its permissions.
I saved the config block in the right client config file.
I set the NAPT_MCP_KEY environment variable (or replaced the placeholder).
I restarted Claude / Cursor after updating the config.
I sent a test prompt like 'Search NAPT templates for VLAN' and got a response.

Troubleshooting

If a checklist step isn't working, find the matching failure below and follow the fix.

MCP key not recognised or returns 401

Likely cause: The key was created but the wrong value was copied, or the key has expired / been revoked.

Open /mcp/keys and click Reveal on your key to confirm the exact value.
Check the Expiry column — expired keys return 401.
If unsure, rotate the key and copy the new value immediately.
Make sure the key has at least the read permission scope.

Claude / Cursor says 'No MCP server found'

Likely cause: The config file path is wrong, the JSON syntax is invalid, or the server block is nested incorrectly.

Claude Desktop: verify the file is named claude_desktop_config.json and lives in the path shown in Settings → Developer → Edit Config.
Cursor: verify the file is ~/.cursor/mcp.json (not .cursorrc or settings.json).
Paste the JSON into jsonlint.com — look for trailing commas or missing braces.
Ensure the NAPT block is directly under mcpServers, not under another server name.

NAPT_MCP_KEY env variable is missing or empty

Likely cause: The placeholder was not replaced, or the env block is outside the NAPT server object.

Replace napt_mcp_... with the real key value, or keep the env block and set NAPT_MCP_KEY in your shell profile.
Restart the terminal / OS after updating shell profile so the variable is exported.
Quick test: open a terminal and run echo $NAPT_MCP_KEY — it should print the key.
If you use a key manager (1Password, etc.), reference it via command args instead of the env block.

Tools still don't appear after saving config

Likely cause: The client caches the old config, or the MCP process crashed on start-up.

Fully quit Claude / Cursor (not just close the window) and reopen it.
Claude Desktop: open the MCP log panel (Settings → Developer → MCP Logs) and look for start-up errors.
Cursor: open the Output panel, choose 'MCP' from the dropdown, and check for spawn errors.
If you see EACCES or command not found, npx may not be in your PATH — switch to a full path like /usr/local/bin/npx.

Test prompt returns 'I don't have access to that tool'

Likely cause: The MCP server started but the client did not register the tools, or the key lacks the required scope.

Wait 10–15 seconds after client start-up for tool discovery to finish.
Verify the key has the generate scope if you are asking for script generation.
Try a simpler prompt first: 'List your available tools' — this confirms the connection without invoking NAPT logic.
If the tool list is empty, restart the client once more and check the MCP logs for JSON-RPC errors.

Docs

Everything you need to go deeper with the NAPT MCP server.