Packetrove

Connect Packetrove to an AI agent

Connect a compatible MCP client to calculate covering CIDRs or inspect the connection used by that client. Start with the setup below, then use the tool examples.

Streamable HTTP · No account or API key required

https://api.packetrove.com/mcp

Connect your client

With Claude Code or Codex installed, add this remote server. These commands configure the client; they do not install a local Packetrove server.

Claude Code

claude mcp add --transport http --scope user packetrove \
  https://api.packetrove.com/mcp
Claude Code MCP documentation

Codex

codex mcp add packetrove \
  --url https://api.packetrove.com/mcp
Codex MCP documentation

Use /mcp in your client to inspect the connection. Confirm that smallest_covering_cidr and public-ip are available.

After configuration, the client discovers available tools with tools/list. Tool descriptions and schemas guide selection and arguments. Reading a web page does not configure a client or grant it tool access.

Use this calculator through MCP

Ask an AI agent to calculate one covering CIDR for a selected group of firewall allowlist or blocklist entries and explain the extra coverage.

Tool name: smallest_covering_cidr

Server address: https://api.packetrove.com/mcp

Streamable HTTP · No account or API key required

Accept 1 to 1,000 IPv4 or IPv6 addresses or CIDRs, up to 64 characters each. Use one address family per call.

Example arguments

{
  "inputs": [
    "203.0.113.1",
    "203.0.113.2",
    "203.0.113.6"
  ]
}

Example result using documentation addresses

{
  "family": "ipv4",
  "normalizedInputs": [
    "203.0.113.1/32",
    "203.0.113.2/32",
    "203.0.113.6/32"
  ],
  "cidr": "203.0.113.0/29",
  "range": {
    "first": "203.0.113.0",
    "last": "203.0.113.7"
  },
  "inputAddressCount": "3",
  "coveredAddressCount": "8",
  "additionalAddressCount": "5"
}

Read cidr and range for the covered network. Check additionalAddressCount before using it in firewall rules. All address counts are decimal strings so IPv6 values stay exact.

Remote MCP calls send your inputs to the server. The browser calculator runs locally. This tool calculates one CIDR; choosing several merges to meet a whole-list entry limit requires a separate decision. It never changes firewall rules.

Open the browser calculator

Inspect a connection through MCP

Ask an AI agent to inspect the public IP observed for the connection making its MCP tool call.

Tool name: public-ip

Server address: https://api.packetrove.com/mcp

Streamable HTTP · No account or API key required

Pass an empty object, {}. The tool observes the request connection; it does not accept an IP address to look up.

Example arguments

{}

Example result using documentation addresses

{
  "ip": "203.0.113.1",
  "family": "ipv4"
}

The example uses a documentation address. A real call returns the observed ip and its family, either ipv4 or ipv6, for that request.

A hosted AI client can return its own exit address. To inspect your browser connection, use this web tool; to inspect your computer’s command-line connection, run the CLI on that computer. One call does not discover both families, private local addresses, or an address before a proxy. The result is not an identity proof.

Check my browser’s public IP

Read results and handle errors

Read structuredContent, or the JSON in the text content block. Keep address counts as decimal strings or arbitrary-precision integers; converting large IPv6 counts to floating-point numbers loses precision.

If isError is true, read the error JSON before retrying. Correct INVALID_INPUT and MIXED_ADDRESS_FAMILIES using the user’s information. CLIENT_IP_UNAVAILABLE means trusted connection metadata is missing; do not invent an address.

Read the technical MCP guide in the repository (English)