NetPilot

NetPilot in Claude, ChatGPT, Gemini, Codex and any MCP assistant

NetPilot adds a network lab to the AI assistant you already use. Connect it once, then ask Claude, ChatGPT, Gemini, Claude Code, Codex, Cursor, VS Code with GitHub Copilot, Meta Muse or any other MCP assistant to design a topology, deploy it on real network operating systems, run commands on the devices and hand you the verified configs for your change window. The lab runs on your own NetPilot lab VM, so the devices, the configs and the designs are yours.

What you need

  • A NetPilot account on Pro, Max, Team or Signature. A Team seat or a Signature seat in an organization counts, which covers Enterprise customers on NetPilot cloud. A dedicated or on-prem Enterprise deployment has its own endpoint: ask your NetPilot contact for it. On Free or Plus the tools answer with a note that the feature starts at Pro.
  • A lab VM. You do not have to create it first: the first time you ask the assistant to start the lab, NetPilot creates the VM for your account, the same way the Start button in the web app does.
  • An assistant that supports remote MCP servers with OAuth sign-in: Claude, ChatGPT, Gemini, Claude Code, Codex, Cursor, VS Code with GitHub Copilot, Meta Muse or any other MCP client. Each client's own plan and workspace policy decide whether you can add one.

Public URL

https://agent.netpilot.io/mcp

Paste this when a client asks for the server URL. Sign-in uses your NetPilot account, and the assistant asks for one permission: NetPilot agent access. No API key is needed.

How to connect

When NetPilot is listed in your assistant's directory, connect it from there. Until then, or on a client without a listing, add it by URL. Both paths end at the same sign-in.

Claude.ai

Available on Free, Pro, Max, Team and Enterprise Claude plans. A Free account can hold one custom connector, so remove another one first if the Add option is blocked.

NetPilot is listed in the Claude directory: claude.ai/directory/netpilot. The written walkthrough with the frames and the lab files: NetPilot in Claude, a Cisco OSPF lab from the chat, and a multi-vendor eBGP lab on Arista, Nokia and FRR from one prompt.

  1. 1Open the NetPilot listing in the Claude directory, or in a chat open the + menu, then Connectors, Add connector and Browse, and search for NetPilot. Click Connect and sign in with your NetPilot account.
  2. 2To add it by URL, click + Add, then Add custom connector. Name it NetPilot, paste https://agent.netpilot.io/mcp and click Continue.
  3. 3Claude detects NetPilot's sign-in. Keep the detected authentication settings, choose Sign in now, leave the OAuth client choice at its default, add no headers or API keys, then click Add and sign in with your NetPilot account.
  4. 4In a chat, open the + menu, choose Connectors and switch NetPilot on. If you chose Sign in when needed instead, Claude asks you to sign in the first time it uses a tool.
  5. 5On Team and Enterprise, an owner adds NetPilot under Organization settings, then Connectors, and each member connects from Customize.

Claude Code and Codex

Add NetPilot from the terminal with one command. Your browser opens the NetPilot sign-in, and the tools are ready in your next session.

  1. 1Claude Code: run claude mcp add --transport http --scope user netpilot https://agent.netpilot.io/mcp, then type /mcp in a session, pick netpilot and sign in.
  2. 2Codex: run codex mcp add netpilot --url https://agent.netpilot.io/mcp and sign in when the browser opens. If you close it, run codex mcp login netpilot.
  3. 3Ask for a lab in the same terminal, for example: start my NetPilot lab and build two FRR routers running OSPF.

Cursor

Cursor signs in with NetPilot's own Cursor client ID, so add the server with the auth block below. It works in the Cursor editor and the Cursor CLI.

  1. 1Open ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project, and add the netpilot entry below.
  2. 2Open Cursor Settings, then MCP, and sign in next to netpilot with your NetPilot account. In the Cursor CLI, run agent mcp enable netpilot, then agent mcp login netpilot.
  3. 3Ask the agent for a lab, for example: start my NetPilot lab and build two FRR routers running OSPF.
{
  "mcpServers": {
    "netpilot": {
      "url": "https://agent.netpilot.io/mcp",
      "auth": {
        "CLIENT_ID": "U9n0sGSiCNoWTdJu",
        "scopes": ["netpilot:agent", "offline_access"]
      }
    }
  }
}

VS Code with GitHub Copilot

VS Code adds NetPilot as an HTTP MCP server and signs in for you. The tools appear in Copilot Chat in agent mode.

  1. 1Run MCP: Add Server from the Command Palette, choose HTTP, paste https://agent.netpilot.io/mcp and name it netpilot. Or add the entry below to .vscode/mcp.json or your user mcp.json.
  2. 2Start the server when VS Code offers to, and sign in with your NetPilot account when the browser opens.
  3. 3Open Copilot Chat, switch to Agent, check that the NetPilot tools are on in the tools list, and ask for a lab.
{
  "servers": {
    "netpilot": {
      "type": "http",
      "url": "https://agent.netpilot.io/mcp"
    }
  }
}

ChatGPT

NetPilot is in ChatGPT's plugin directory. Install it from the NetPilot listing in ChatGPT, on the web, and ask for a lab in any chat. The ChatGPT walkthrough shows every click, and the multi-vendor run builds a Cisco, Arista and Junos lab from one prompt.

  1. 1Open the NetPilot listing (Plugins in ChatGPT, search NetPilot) and click Install plugin.
  2. 2On the NetPilot page that opens, sign in with your NetPilot account and click Connect to ChatGPT. You land back in ChatGPT with the plugin installed.
  3. 3Click Try in chat, or type @ in any chat and pick NetPilot, then ask for a lab, for example: make me a CCNA practice lab as a Packet Tracer file.

To add it by URL instead, for example on a workspace where plugins are managed, use a custom MCP server. Which ChatGPT plans can add one with write tools is set by OpenAI, see OpenAI's custom MCP server guide, and ask your workspace admin if the option is missing there.

  1. 1Click +, then Add custom MCP server. Name it NetPilot, paste https://agent.netpilot.io/mcp, choose OAuth as the authentication, read and accept the warning about custom servers, then choose Create as a plugin.
  2. 2Review the tools ChatGPT discovered. Then open your personal plugins (chatgpt.com/plugins, Personal tab), open NetPilot and select the plus button to install it.
  3. 3Start a Work chat, type @ and pick NetPilot. Sign in with your NetPilot account when ChatGPT asks.

Gemini

NetPilot connects to the Gemini app on the web as a custom connector. Google offers custom connectors on personal Google accounts in the United States. For lab work, choose a paid model such as Gemini 3.1 Pro or Gemini 3.8 Flash on a Google AI plan: they run the full lab workflow and quote the device output.

  1. 1Open gemini.google.com, then Settings (Customize on some accounts), then Connectors.
  2. 2Click + Custom, paste https://agent.netpilot.io/mcp and click Connect.
  3. 3Sign in with your NetPilot account and click Connect on the NetPilot page.
  4. 4Ask Gemini for a lab, for example: start my NetPilot lab and build two FRR routers running OSPF.

Meta Muse

Connectors live under Settings in Muse. Meta offers Muse to people in the United States and Canada who are 18 and over, so the steps below apply there.

  1. 1Open Settings, then Connectors. Tap Connect next to NetPilot, read the information, tap Continue and sign in with your NetPilot account.
  2. 2If NetPilot is not listed yet, ask Muse to create a custom connector and give it https://agent.netpilot.io/mcp.
  3. 3Disconnect at any time under Settings, then Connectors.

Any other MCP assistant

NetPilot is a standard remote MCP server, so an assistant or editor that can add a remote MCP server with OAuth sign-in connects the same way.

  1. 1Open the client's MCP server settings and add a remote server, sometimes called streamable HTTP. Name it NetPilot and paste https://agent.netpilot.io/mcp.
  2. 2Leave the authentication on OAuth with no client ID, header or API key. The client opens the NetPilot sign-in.
  3. 3Sign in with your NetPilot account and click Connect. The page names the client by its web address, so check that it is the one you are adding.

What the assistant can do with NetPilot

Nineteen tools in three groups. The assistant picks them for you. You ask for the outcome.

Your lab VM

Start, stop and check the lab VM that runs your devices.

  • Start the VM. On first use NetPilot creates it for you.
  • Stop the VM and see the lab credits the session used.
  • Check status: running or stopped, time until the idle stop, vendor images on the VM, the labs deployed on it and the link of the lab viewer when one is open. The assistant reads this first and picks the next step from it.
  • Open the lab viewer for a deployed lab and hand you its link: the topology with a web console on every device, open while the VM runs.

Design and Cisco Packet Tracer

Turn a description into a topology and configs, and hand them to you in the format you work in.

  • Design a topology from plain English and read it back.
  • Generate the device configs for each vendor in the design and read them back.
  • Export the design as a Cisco Packet Tracer .pkt file and download it from your NetPilot account.
  • Vendor guide: how each supported network OS is configured, from Nokia SR Linux and FRRouting to Cisco IOL, Arista cEOS and Juniper cRPD, so the assistant writes the right syntax the first time. The supported devices page lists every network OS the lab runs.

Deploy and operate

Run the lab on real network operating systems and work on the devices.

  • Push the topology and the configs to the VM and deploy the lab with containerlab.
  • Run show and configuration commands on any device, and drive interactive dialogs such as a password or a confirmation prompt.
  • Run shell commands on the VM, start long jobs in the background and read their output later.
  • The result is the lab viewer link, the verified configs and the show output you carry into your change ticket or your cutover plan.

Permissions, limits and errors

  • Permission: one sign-in with your NetPilot account grants NetPilot agent access to the connected assistant. No API key, and the assistant never sees your NetPilot password.
  • Read and write: checking status, reading a design or a config, the vendor guide and reading a job's output are read-only. Claude runs them without a prompt unless your organization sets NetPilot or a tool to Needs approval, and Muse asks once on first use and then offers Always allow. Starting or stopping the VM, deploying a lab, pushing configs and running commands on devices change state, and clients that confirm destructive actions ask you first.
  • Side effects: a deploy or a device command runs on your lab VM only. Starting the VM spends lab credits until it stops.
  • Limits per account: 60 lab calls a minute, 20 VM start or stop calls a minute, 30 VM starts an hour, 30 design calls a minute, and two lab calls running at the same time. A single call runs for at most 16 minutes, so long jobs run in the background and the assistant reads their output afterwards.
  • Errors: every error names the cause and the next step, for example that the VM is stopped and needs starting, that it is still starting, that the lab credits for the month are used up, or that a feature starts at Pro. A VM that is briefly unreachable answers with a retry in 30 seconds.

Lab credits and the idle timeout

A lab started from an assistant uses the same lab credits as a lab started in the web app: Pro includes 50 a month, Team 60 per seat, Max 150, and Signature covers lab usage under fair use for your agreed scope. A session is charged when the VM stops. The VM stops itself when nothing has used it for 1 hour on Pro and Team, or 2 hours on Max and Signature. Lab commands count as activity, status checks do not. A stopped VM keeps its labs for 14 days on Pro and Team, and for as long as the account exists on Max and Signature. Start the VM again before that period ends and the labs are back where you left them. The pricing page has the plan details.

Questions about NetPilot in an assistant

NetPilot keeps the topology designs and generated configs you create, plus the state of your lab VM, in your NetPilot account. It receives only the requests the assistant sends to its tools, such as a topology description or a device command, and returns the result. The rest of the conversation stays with the assistant and is covered by that provider's privacy policy. The NetPilot privacy policy lists the retention periods.
Remove it in the assistant's own settings: Customize > Connectors in Claude, the Plugins page in ChatGPT, Settings > Connectors in Gemini and in Muse, claude mcp remove netpilot in Claude Code, codex mcp remove netpilot in Codex, the MCP settings in Cursor and VS Code, or the MCP server list of any other client. The assistant loses access within a minute. Your NetPilot account, labs and designs stay as they are, and you can connect again at any time.
Pro, Max, Team or Signature, including a Team seat or a Signature seat in an organization. On Free or Plus you can connect and sign in, and each tool answers with a note that the feature is included from Pro. The plans are listed on the pricing page.
No. The assistant runs its own model, billed by that provider. NetPilot charges lab credits for the time your lab VM runs, exactly as it does for a lab started in the web app.
Yes. Your account has one lab VM, and every assistant and the web app work on it. A lab deployed from Claude shows up in the web app, and a lab started in the app is visible to ChatGPT or Muse. Two assistants writing a design at the same time overwrite each other, so finish one before starting the next.
A cold start of the lab VM can take a few minutes, longer than some assistants wait for one answer. Ask the assistant to check the VM status again. Nothing is lost: the VM finishes starting on its own, and the assistant continues from there.

Watch it from the chat

Two NetPilot channel episodes, one per assistant: in ChatGPT, the plugin installed from the directory, a CCNA lab as a Packet Tracer file and the same lab on real Cisco IOS. In Claude, a multi-area OSPF lab on four Cisco IOS routers built from one prompt and verified by hand on the real CLI.

Packet Tracer Lab From One ChatGPT Prompt, Then Real Cisco IOS · Watch on YouTube
How to Connect NetPilot in Claude and Build a Real Cisco OSPF Lab From the Chat · Watch on YouTube

Build the next lab from the chat you already have open

Create a NetPilot account, pick Pro or above, and connect NetPilot in your assistant.

Stuck on a step? Support