Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cisco Meraki

OCI · GHCR.IO/WYRE-TECHNOLOGY/MERAKI-MCP:V1.1.3 · SCANNED AUG 22

MCP server for the Cisco Meraki Dashboard: networks, devices, wireless, switch, appliance.

38 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2147 tokens (~76/item across 28 items; 27 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Cisco Meraki MCP server?

Cisco Meraki runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-technology/meraki-mcp:v1.1.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/wyre-technology/meraki-mcp:v1.1.3

# add to Claude Code
claude mcp add wyre-technology-meraki-mcp -- docker run --rm -i ghcr.io/wyre-technology/meraki-mcp:v1.1.3
// .cursor/mcp.json
{
  "mcpServers": {
    "wyre-technology-meraki-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wyre-technology-meraki-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add wyre-technology-meraki-mcp -- docker run --rm -i ghcr.io/wyre-technology/meraki-mcp:v1.1.3
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-technology-meraki-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  wyre-technology-meraki-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wyre-technology-meraki-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "wyre-technology-meraki-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Aug 26 38

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Aug 2026 · Analysed oci/ghcr.io/wyre-technology/meraki-mcp:v1.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published
MCP tools · 27 exposed · ~2,130 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
meraki_appliance_firewall_l3_get ~38

Get the layer 3 firewall rules for an MX appliance network.

NameTypeReqDescription
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_appliance_firewall_l3_update ~165

⚠ HIGH-IMPACT. Replaces the layer 3 firewall rule set for an MX appliance network. This changes what traffic is allowed or denied and takes effect immediately; a bad rule set can cut off network access. Reversible by re-applying the previous rules, but the change is applied over the same link it can sever. Requires confirm_destructive_action: true. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm replacing the entire L3 firewall rule set. Any rule not present in `rules` is deleted.
network_idstringyesNetwork ID
rulesarrayyesThe ordered list of L3 firewall rules to apply (replaces the existing set).

No output schema declared.

No examples provided.

meraki_appliance_vpn_status_get ~37

Get the site-to-site VPN configuration for an MX appliance network.

NameTypeReqDescription
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_clients_get ~46

Get a single client on a network by client ID or MAC.

NameTypeReqDescription
client_idstringyesClient ID or MAC address
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_clients_get_policy ~43

Get the network policy assigned to a client.

NameTypeReqDescription
client_idstringyesClient ID or MAC address
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_clients_list ~63

List clients seen on a network within a time window.

NameTypeReqDescription
network_idstringyesNetwork ID
per_pagenumberResults per page
timespannumberTimespan in seconds to look back (max 2592000)

No output schema declared.

No examples provided.

meraki_clients_update_policy ~186

⚠ HIGH-IMPACT. Updates the network access policy for a client (e.g. Normal, Blocked, Allowed, or a group policy). Takes effect immediately and can revoke or grant network access for the device. Reversible by reassigning the policy, but a blocked client loses the connection it would need to report the problem. Requires confirm_destructive_action: true. Confirm with the user before invoking.

NameTypeReqDescription
client_idstringyesClient ID or MAC address
confirm_destructive_actionbooleanMust be true to confirm changing this client's network access. Setting "Blocked" cuts the device off the network immediately.
device_policystringyesThe policy to apply to the client
group_policy_idstringGroup policy ID (required when device_policy is "Group policy")
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_devices_get ~28

Get a single device by serial number.

NameTypeReqDescription
serialstringyesDevice serial number

No output schema declared.

No examples provided.

meraki_devices_list ~27

List the devices in a network.

NameTypeReqDescription
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_devices_reboot ~114

⚠ HIGH-IMPACT. Reboots a Meraki device, causing a temporary loss of connectivity for clients served by it — including, if this is the gateway, the link carrying this request. Service resumes automatically after the reboot. Requires confirm_destructive_action: true. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm rebooting the device. Clients served by it lose connectivity until it comes back up.
serialstringyesDevice serial number

No output schema declared.

No examples provided.

meraki_devices_remove ~98

⚠ DESTRUCTIVE — IRREVERSIBLE. Removes a device from its network, unclaiming its configuration and returning it to organization inventory. This action cannot be undone. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm removing the device from its network.
network_idstringyesNetwork ID the device belongs to
serialstringyesDevice serial number

No output schema declared.

No examples provided.

meraki_navigate ~141

Discover available Cisco Meraki tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

NameTypeReqDescription
domainstringyesThe domain to explore: - organizations: list/get organizations, list inventory devices - networks: list/get/update/delete networks within an organization - devices: list/get devices, reboot, remove f…

No output schema declared.

No examples provided.

meraki_networks_delete ~74

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a network and all of its configuration. This action cannot be undone. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm this irreversible deletion.
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_networks_get ~28

Get a single network by ID.

NameTypeReqDescription
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_networks_list ~50

List the networks belonging to an organization.

NameTypeReqDescription
organization_idstringyesOrganization ID
per_pagenumberResults per page
starting_afterstringPagination cursor

No output schema declared.

No examples provided.

meraki_networks_update ~177

⚠ HIGH-IMPACT. Updates a network's configuration (name, time zone, tags, notes). Changes take effect immediately across the network and are visible to operators. Reversible by reverting the fields, but `tags` REPLACES the existing list rather than merging, so omitted tags are dropped. Requires confirm_destructive_action: true. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm updating this network. Any tag not present in `tags` is dropped.
namestringNew network name
network_idstringyesNetwork ID
notesstringNetwork notes
tagsarrayReplacement tag list
timeZonestringNew IANA time zone (e.g. "America/Chicago")

No output schema declared.

No examples provided.

meraki_organizations_get ~28

Get a single organization by ID.

NameTypeReqDescription
organization_idstringyesOrganization ID

No output schema declared.

No examples provided.

meraki_organizations_inventory_list ~50

List inventory devices for an organization.

NameTypeReqDescription
organization_idstringyesOrganization ID
per_pagenumberResults per page
starting_afterstringPagination cursor

No output schema declared.

No examples provided.

meraki_organizations_list ~21

List the organizations accessible to the configured API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

meraki_raw_request ~172

Escape hatch for the long tail of the Meraki Dashboard API. Reaches ANY Meraki v1 endpoint not covered by a curated tool. The call is classified by HTTP method — GET is a read; POST/PUT/DELETE are writes and are subject to read-only mode; DELETE is destructive and requires confirm_destructive_action. Prefer a curated tool when one exists; confirm write/destructive calls with the user before invoking.

NameTypeReqDescription
bodyobjectOptional JSON request body
confirm_destructive_actionbooleanMust be true to confirm a DELETE (destructive) request.
methodstringyesHTTP method
pathstringyesMeraki v1 API path, e.g. "/organizations/{id}/networks"
queryobjectOptional query string parameters

No output schema declared.

No examples provided.

meraki_status ~23

Check Meraki API connection status, configured organization, and available domains.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

meraki_switch_port_statuses_list ~50

List live status and traffic counters for the ports on a switch.

NameTypeReqDescription
serialstringyesSwitch serial number
timespannumberTimespan in seconds for counters

No output schema declared.

No examples provided.

meraki_switch_ports_list ~29

List the ports configured on a switch.

NameTypeReqDescription
serialstringyesSwitch serial number

No output schema declared.

No examples provided.

meraki_switch_ports_update ~183

⚠ HIGH-IMPACT. Updates a switch port's configuration (name, enabled state, VLAN, type, PoE, etc.). Changes take effect immediately and can disrupt connectivity for devices on that port — including the uplink carrying this request. Reversible by reverting the settings, if you still have a path to the switch. Requires confirm_destructive_action: true. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm reconfiguring this port. Disabling it or moving its VLAN can cut off the devices behind it.
port_idstringyesPort ID (e.g. "1")
serialstringyesSwitch serial number
settingsobjectyesPort settings to apply (e.g. { name, enabled, vlan, type, poeEnabled, ... }).

No output schema declared.

No examples provided.

meraki_wireless_rf_profiles_list ~32

List the RF profiles configured on a network.

NameTypeReqDescription
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_wireless_ssids_list ~33

List the wireless SSIDs configured on a network.

NameTypeReqDescription
network_idstringyesNetwork ID

No output schema declared.

No examples provided.

meraki_wireless_ssids_update ~194

⚠ HIGH-IMPACT. Updates a wireless SSID's configuration (name, enabled state, auth mode, PSK, VLAN, etc.). Changes are broadcast immediately and can disconnect clients or change network access. Changing the PSK or auth mode drops every client on the SSID and they cannot rejoin with the old credentials. Reversible by reverting the settings. Requires confirm_destructive_action: true. Confirm with the user before invoking.

NameTypeReqDescription
confirm_destructive_actionbooleanMust be true to confirm reconfiguring this SSID. Changing the PSK, auth mode or enabled state disconnects every client currently on it.
network_idstringyesNetwork ID
numbernumberyesSSID number (0-14)
settingsobjectyesSSID settings to apply (e.g. { name, enabled, authMode, psk, ... }).

No output schema declared.

No examples provided.

Common questions

What is the Cisco Meraki MCP server?

Cisco Meraki is an MCP server listed in the public MCP registry as io.github.wyre-technology/meraki-mcp. MCP server for the Cisco Meraki Dashboard: networks, devices, wireless, switch, appliance. This page covers its container image (ghcr.io/wyre-technology/meraki-mcp:v1.1.3).

Is the Cisco Meraki MCP server safe to use?

Cisco Meraki scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Cisco Meraki MCP server expose?

Cisco Meraki exposes 27 tools: meraki_navigate, meraki_status, meraki_organizations_list, meraki_organizations_get, meraki_organizations_inventory_list, and 22 more. Their descriptions and schemas cost roughly 2,130 tokens of context every time the server is loaded.

Is the Cisco Meraki MCP server still maintained?

Cisco Meraki is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Cisco Meraki MCP server under?

Cisco Meraki declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.