Cisco Meraki
OCI · GHCR.IO/WYRE-TECHNOLOGY/MERAKI-MCP:V1.1.3
MCP server for the Cisco Meraki Dashboard: networks, devices, wireless, switch, appliance.
Available components
Last scanned (1 hour ago)
Scores higher than 73% of OCI servers
Category Cloud Infrastructure
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 → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −3
- Stability: pass → 0.83 functional
- 10 Oct 26 +1
- Stability: 0.97 → pass security
- 9 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 80 to 97. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 +1
- Stability: 0.97 → pass security
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 17 Oct 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 |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
meraki_appliance_firewall_l3_get ~38
Get the layer 3 firewall rules for an MX appliance network.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Network ID |
| rules | array | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_clients_get ~46
Get a single client on a network by client ID or MAC.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | Client ID or MAC address |
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_clients_get_policy ~43
Get the network policy assigned to a client.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | Client ID or MAC address |
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_clients_list ~63
List clients seen on a network within a time window.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network ID |
| per_page | number | – | Results per page |
| timespan | number | – | Timespan 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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | 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 | yes | The policy to apply to the client |
| group_policy_id | string | – | Group policy ID (required when device_policy is "Group policy") |
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_devices_get ~28
Get a single device by serial number.
| Name | Type | Req | Description |
|---|---|---|---|
| serial | string | yes | Device serial number |
No output schema declared.
No examples provided.
meraki_devices_list ~27
List the devices in a network.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Device 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_destructive_action | boolean | – | Must be true to confirm removing the device from its network. |
| network_id | string | yes | Network ID the device belongs to |
| serial | string | yes | Device 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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… |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_destructive_action | boolean | – | Must be true to confirm this irreversible deletion. |
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_networks_get ~28
Get a single network by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_networks_list ~50
List the networks belonging to an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id | string | yes | Organization ID |
| per_page | number | – | Results per page |
| starting_after | string | – | Pagination 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Network ID |
| notes | string | – | Network notes |
| tags | array | – | Replacement tag list |
| timeZone | string | – | New IANA time zone (e.g. "America/Chicago") |
No output schema declared.
No examples provided.
meraki_organizations_get ~28
Get a single organization by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id | string | yes | Organization ID |
No output schema declared.
No examples provided.
meraki_organizations_inventory_list ~50
List inventory devices for an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id | string | yes | Organization ID |
| per_page | number | – | Results per page |
| starting_after | string | – | Pagination 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Optional JSON request body |
| confirm_destructive_action | boolean | – | Must be true to confirm a DELETE (destructive) request. |
| method | string | yes | HTTP method |
| path | string | yes | Meraki v1 API path, e.g. "/organizations/{id}/networks" |
| query | object | – | Optional 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.
| Name | Type | Req | Description |
|---|---|---|---|
| serial | string | yes | Switch serial number |
| timespan | number | – | Timespan in seconds for counters |
No output schema declared.
No examples provided.
meraki_switch_ports_list ~29
List the ports configured on a switch.
| Name | Type | Req | Description |
|---|---|---|---|
| serial | string | yes | Switch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Port ID (e.g. "1") |
| serial | string | yes | Switch serial number |
| settings | object | yes | Port 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.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network ID |
No output schema declared.
No examples provided.
meraki_wireless_ssids_list ~33
List the wireless SSIDs configured on a network.
| Name | Type | Req | Description |
|---|---|---|---|
| network_id | string | yes | Network 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Network ID |
| number | number | yes | SSID number (0-14) |
| settings | object | yes | SSID settings to apply (e.g. { name, enabled, authMode, psk, ... }). |
No output schema declared.
No examples provided.
How do I install the Cisco Meraki MCP server?
Cisco Meraki runs locally as a container image, launched with docker run --rm -i -e MERAKI_API_KEY -e MERAKI_ORG_ID -e MERAKI_BASE_URL -e READ_ONLY_MODE -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL 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
claude mcp add wyre-technology-meraki-mcp -- docker run --rm -i -e MERAKI_API_KEY -e MERAKI_ORG_ID -e MERAKI_BASE_URL -e READ_ONLY_MODE -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/meraki-mcp:v1.1.3
This image reads MERAKI_API_KEY, MERAKI_ORG_ID, MERAKI_BASE_URL, READ_ONLY_MODE, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
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 49 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 17 October 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.