Meraki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ROLE | No | One of noc, sysadmin, all (defaults to noc) | noc |
| MERAKI_KEY | Yes | Your Meraki Dashboard API key | |
| MERAKI_BASE_URL | No | Defaults to https://api.meraki.com/api/v1 | https://api.meraki.com/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| updateNetworkFirmwareUpgradesC | Update firmware upgrade information for a network |
| getOrganizationsA | List the organizations that the user has privileges on |
| getOrganizationDevicesB | List the devices in an organization that have been assigned to a network. |
| getOrganizationFirmwareUpgradesC | Get firmware upgrade information for an organization |
| getOrganizationLicensesOverviewA | Return an overview of the license state for an organization |
| getOrganizationNetworksB | List the networks that the user has privileges on in an organization |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: organizations, devices, firmware upgrades at org/network level, licenses, and networks. The only potentially confusing pair (get vs update firmware) is clearly separated by verb and scope, leaving no ambiguity.
All tool names follow a consistent verb-first camelCase pattern: 'get' for read operations and 'update' for the single write operation. The pattern is uniformly applied across resources, with no mixing of conventions.
The server has 6 tools, which is well within the ideal 3-15 range. Each tool covers a meaningful aspect of the Meraki domain, and the set feels neither sparse nor bloated.
The server covers core organization-level reads (orgs, networks, devices, firmware, licenses) and one update for network firmware. Minor gaps exist, such as no per-network device listing or create/delete operations, but these are acceptable for a focused read-heavy server.