# Cisco Meraki (oci · ghcr.io/wyre-technology/meraki-mcp:v1.1.3)

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

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/wyre-technology/meraki-mcp:v1.1.3`: 38/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-meraki-mcp/ghcr-io-wyre-technology-meraki-mcp-v1-1-3.md), [page](https://verifymcp.io/servers/wyre-technology-meraki-mcp/ghcr-io-wyre-technology-meraki-mcp-v1-1-3)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/meraki-mcp:v1.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2147 tokens (~76/item across 28 items; 27 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**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.

### Claude

```bash
claude mcp add wyre-technology-meraki-mcp -- docker run --rm -i ghcr.io/wyre-technology/meraki-mcp:v1.1.3
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-technology-meraki-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-technology-meraki-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
```

### Codex

```bash
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

```yaml
mcp_servers:
  wyre-technology-meraki-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-technology-meraki-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-technology-meraki-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/meraki-mcp:v1.1.3"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 38)

First indexed and scored.

## MCP tools (27)

### `meraki_navigate` (~141 tokens)

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.

Input parameters:

- `domain` (string, required): The 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…

### `meraki_status` (~23 tokens)

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

### `meraki_organizations_list` (~21 tokens)

List the organizations accessible to the configured API key.

### `meraki_organizations_get` (~28 tokens)

Get a single organization by ID.

Input parameters:

- `organization_id` (string, required): Organization ID

### `meraki_organizations_inventory_list` (~50 tokens)

List inventory devices for an organization.

Input parameters:

- `organization_id` (string, required): Organization ID
- `per_page` (number): Results per page
- `starting_after` (string): Pagination cursor

### `meraki_networks_list` (~50 tokens)

List the networks belonging to an organization.

Input parameters:

- `organization_id` (string, required): Organization ID
- `per_page` (number): Results per page
- `starting_after` (string): Pagination cursor

### `meraki_networks_get` (~28 tokens)

Get a single network by ID.

Input parameters:

- `network_id` (string, required): Network ID

### `meraki_networks_update` (~177 tokens)

⚠ 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.

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm updating this network. Any tag not present in `tags` is dropped.
- `name` (string): New network name
- `network_id` (string, required): Network ID
- `notes` (string): Network notes
- `tags` (array): Replacement tag list
- `timeZone` (string): New IANA time zone (e.g. "America/Chicago")

### `meraki_networks_delete` (~74 tokens)

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

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm this irreversible deletion.
- `network_id` (string, required): Network ID

### `meraki_devices_list` (~27 tokens)

List the devices in a network.

Input parameters:

- `network_id` (string, required): Network ID

### `meraki_devices_get` (~28 tokens)

Get a single device by serial number.

Input parameters:

- `serial` (string, required): Device serial number

### `meraki_devices_reboot` (~114 tokens)

⚠ 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.

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm rebooting the device. Clients served by it lose connectivity until it comes back up.
- `serial` (string, required): Device serial number

### `meraki_devices_remove` (~98 tokens)

⚠ 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.

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm removing the device from its network.
- `network_id` (string, required): Network ID the device belongs to
- `serial` (string, required): Device serial number

### `meraki_clients_list` (~63 tokens)

List clients seen on a network within a time window.

Input parameters:

- `network_id` (string, required): Network ID
- `per_page` (number): Results per page
- `timespan` (number): Timespan in seconds to look back (max 2592000)

### `meraki_clients_get` (~46 tokens)

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

Input parameters:

- `client_id` (string, required): Client ID or MAC address
- `network_id` (string, required): Network ID

### `meraki_clients_get_policy` (~43 tokens)

Get the network policy assigned to a client.

Input parameters:

- `client_id` (string, required): Client ID or MAC address
- `network_id` (string, required): Network ID

### `meraki_clients_update_policy` (~186 tokens)

⚠ 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.

Input parameters:

- `client_id` (string, required): Client ID or MAC address
- `confirm_destructive_action` (boolean): Must be true to confirm changing this client's network access. Setting "Blocked" cuts the device off the network immediately.
- `device_policy` (string, required): The policy to apply to the client
- `group_policy_id` (string): Group policy ID (required when device_policy is "Group policy")
- `network_id` (string, required): Network ID

### `meraki_wireless_ssids_list` (~33 tokens)

List the wireless SSIDs configured on a network.

Input parameters:

- `network_id` (string, required): Network ID

### `meraki_wireless_ssids_update` (~194 tokens)

⚠ 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.

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm reconfiguring this SSID. Changing the PSK, auth mode or enabled state disconnects every client currently on it.
- `network_id` (string, required): Network ID
- `number` (number, required): SSID number (0-14)
- `settings` (object, required): SSID settings to apply (e.g. { name, enabled, authMode, psk, ... }).

### `meraki_wireless_rf_profiles_list` (~32 tokens)

List the RF profiles configured on a network.

Input parameters:

- `network_id` (string, required): Network ID

### `meraki_switch_ports_list` (~29 tokens)

List the ports configured on a switch.

Input parameters:

- `serial` (string, required): Switch serial number

### `meraki_switch_ports_update` (~183 tokens)

⚠ 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.

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm reconfiguring this port. Disabling it or moving its VLAN can cut off the devices behind it.
- `port_id` (string, required): Port ID (e.g. "1")
- `serial` (string, required): Switch serial number
- `settings` (object, required): Port settings to apply (e.g. { name, enabled, vlan, type, poeEnabled, ... }).

### `meraki_switch_port_statuses_list` (~50 tokens)

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

Input parameters:

- `serial` (string, required): Switch serial number
- `timespan` (number): Timespan in seconds for counters

### `meraki_appliance_firewall_l3_get` (~38 tokens)

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

Input parameters:

- `network_id` (string, required): Network ID

### `meraki_appliance_firewall_l3_update` (~165 tokens)

⚠ 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.

Input parameters:

- `confirm_destructive_action` (boolean): Must be true to confirm replacing the entire L3 firewall rule set. Any rule not present in `rules` is deleted.
- `network_id` (string, required): Network ID
- `rules` (array, required): The ordered list of L3 firewall rules to apply (replaces the existing set).

### `meraki_appliance_vpn_status_get` (~37 tokens)

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

Input parameters:

- `network_id` (string, required): Network ID

### `meraki_raw_request` (~172 tokens)

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.

Input parameters:

- `body` (object): Optional JSON request body
- `confirm_destructive_action` (boolean): Must be true to confirm a DELETE (destructive) request.
- `method` (string, required): HTTP method
- `path` (string, required): Meraki v1 API path, e.g. "/organizations/{id}/networks"
- `query` (object): Optional query string parameters

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-technology-meraki-mcp/ghcr-io-wyre-technology-meraki-mcp-v1-1-3#diagnostics

## Score history

- 2026-08-22: 38
- 2026-08-21: 38
- 2026-08-20: 38

## 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.

## Links

- Repository: https://github.com/wyre-technology/meraki-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-meraki-mcp/ghcr-io-wyre-technology-meraki-mcp-v1-1-3.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-meraki-mcp/ghcr-io-wyre-technology-meraki-mcp-v1-1-3.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-meraki-mcp/ghcr-io-wyre-technology-meraki-mcp-v1-1-3