mcp-meraki

MCP运维云端

提供方 paolo-trivi

运维云端 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaude
查看接入方式

A complete Model Context Protocol (MCP) server for Cisco Meraki Dashboard API, enabling management of Meraki networks, devices, and configurations.

一句话选型结论

按资料字段整理

mcp-meraki 属于运维云端类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Local Deployment Network Management API Integration TypeScript Device Control Monitoring Tool Automation

支持客户端

适用场景

Local DeploymentNetwork ManagementAPI Integration

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
node /absolute/path/to/mcp-meraki/dist/index.js

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
mcp-meraki当前 未标注 stdio · 本地进程 本地部署 有 2026-10-06
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方paolo-trivi上游标注的维护方 paolo-trivi
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-10-06上游最后核验时间

详细介绍

11.6 KB
来自项目仓库与上游目录的原文,未做删改

MCP Meraki Server

Complete Model Context Protocol (MCP) server for Cisco Meraki Dashboard API. This server exposes all major Meraki Dashboard API endpoints as MCP tools, enabling Claude to interact with and manage Meraki networks, devices, and configurations.

Features

  • Complete API Coverage: Implements 80+ tools across all major Meraki API categories
  • Rate Limiting: Automatic rate limiting (5 req/sec per org, configurable)
  • Smart Retries: Exponential backoff for failed requests
  • Caching: Intelligent caching for semi-static data
  • Auto-Pagination: Automatic handling of paginated responses
  • Type Safety: Full TypeScript implementation with comprehensive type definitions
  • Error Handling: Detailed error messages with HTTP status codes

Supported API Categories

Core Infrastructure (Priority 1)

  • Organizations: List, get details, inventory, licenses, API usage
  • Networks: CRUD operations, bind/unbind templates, split/combine
  • Devices: List, update, claim, remove, reboot, blink LEDs, LLDP/CDP

Network Equipment (Priority 2)

  • Switch: Port configuration, VLANs, stacks, QoS, routing
  • Wireless: SSIDs, RF profiles, Bluetooth, Air Marshal
  • Appliance: VLANs, firewall rules, VPN, NAT, port forwarding, traffic shaping

Operations & Management (Priority 3)

  • Monitoring: Uplink status, connection stats, latency, events, traffic analysis
  • Alerts: Alert settings, webhooks, HTTP servers
  • Camera: Quality settings, snapshots, video links, MV Sense, analytics

Installation

Prerequisites

  • Node.js 18+ and npm
  • Meraki Dashboard API key (Get one here)
  • Claude Desktop app or compatible MCP client

Setup

  1. Clone or navigate to the project directory:bash cd mcp-meraki

  2. Install dependencies:bash npm install

  3. Configure environment variables:bash cp .env.example .env

Edit .env and set your Meraki API key:env MERAKI_API_KEY=your_api_key_here MERAKI_BASE_URL=https://api.meraki.com/api/v1 MERAKI_RATE_LIMIT=5 MERAKI_TIMEOUT=30000 DEBUG=false

  1. Build the project:bash npm run build

Configuration for Claude Desktop

Add this server to your Claude Desktop configuration file:

macOS/Linux

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:```json
{
"mcpServers": {
"meraki": {
"command": "node",
"args": ["/absolute/path/to/mcp-meraki/dist/index.js"],
"env": {
"MERAKI_API_KEY": "your_api_key_here",
"MERAKI_BASE_URL": "https://api.meraki.com/api/v1",
"MERAKI_RATE_LIMIT": "5"
}
}
}
}


### Windows
Edit `%APPDATA%\Claude\claude_desktop_config.json` with the same structure.

**Important**: Use absolute paths and replace `/absolute/path/to/mcp-meraki` with your actual project path.

## Usage Examples

Once configured, you can ask Claude to interact with your Meraki infrastructure:

### Basic Examples```
"List all my Meraki organizations"
→ Uses: organizations_list

"Show me all networks in organization 123456"
→ Uses: networks_list

"Get details for device with serial Q2HP-ABCD-EFGH"
→ Uses: devices_get

"List all switch ports on device Q2HP-ABCD-EFGH"
→ Uses: switch_ports_list

Advanced Examples```

"Create a new network called 'Branch Office' in org 123456 with wireless and appliance"
→ Uses: networks_create

"Update switch port 1 on device Q2HP-ABCD-EFGH to VLAN 10 and enable PoE"
→ Uses: switch_port_update

"Show me the firewall rules for network L_123456789"
→ Uses: appliance_firewall_l3_rules_get

"Get uplink status for all devices in network L_123456789"
→ Uses: monitoring_uplinks_status

"List all events in the last 24 hours for network L_123456789"
→ Uses: monitoring_events


### Network Operations```
"Show me all SSIDs in network L_123456789"
→ Uses: wireless_ssids_list

"Update SSID 0 in network L_123456789 to use WPA2-PSK with password 'SecurePassword123'"
→ Uses: wireless_ssid_update

"Get VPN settings for network L_123456789"
→ Uses: appliance_vpn_settings_get

"Create a port forwarding rule to forward port 80 to 192.168.1.100:8080"
→ Uses: appliance_port_forwarding_rules_update

Monitoring & Troubleshooting```

"Show me connection statistics for the last hour in network L_123456789"
→ Uses: monitoring_connection_stats

"Get latency stats for network L_123456789"
→ Uses: monitoring_latency_stats

"Show me all clients connected to device Q2HP-ABCD-EFGH"
→ Uses: devices_clients

"Blink the LEDs on device Q2HP-ABCD-EFGH for 30 seconds"
→ Uses: devices_blink_leds


## Complete Tools List

### Organizations (8 tools)
- `organizations_list` - List all organizations
- `organizations_get` - Get organization details
- `organizations_update` - Update organization settings
- `organizations_inventory` - Get device inventory
- `organizations_licenses` - List licenses
- `organizations_license_get` - Get license details
- `organizations_api_requests` - Get API usage history
- `organizations_clone` - Clone organization

### Networks (10 tools)
- `networks_list` - List networks
- `networks_get` - Get network details
- `networks_create` - Create network
- `networks_update` - Update network
- `networks_delete` - Delete network
- `networks_bind` - Bind to template
- `networks_unbind` - Unbind from template
- `networks_split` - Split combined network
- `networks_combine` - Combine networks
- `networks_firmware_upgrades` - Get firmware settings

### Devices (11 tools)
- `devices_list` - List devices
- `devices_get` - Get device details
- `devices_update` - Update device
- `devices_claim` - Claim devices
- `devices_remove` - Remove device
- `devices_blink_leds` - Blink LEDs
- `devices_reboot` - Reboot device
- `devices_clients` - List clients
- `devices_lldp_cdp` - Get LLDP/CDP info
- `devices_loss_latency` - Get loss/latency history
- `devices_management_interface` - Get management interface

### Switch (7 tools)
- `switch_ports_list` - List switch ports
- `switch_port_get` - Get port details
- `switch_port_update` - Update port configuration
- `switch_vlans_list` - List VLANs
- `switch_vlan_create` - Create VLAN
- `switch_stacks_list` - List switch stacks
- `switch_stack_create` - Create switch stack

### Wireless (8 tools)
- `wireless_ssids_list` - List SSIDs
- `wireless_ssid_get` - Get SSID details
- `wireless_ssid_update` - Update SSID
- `wireless_rf_profiles_list` - List RF profiles
- `wireless_rf_profile_create` - Create RF profile
- `wireless_bluetooth_get` - Get Bluetooth settings
- `wireless_bluetooth_update` - Update Bluetooth settings
- `wireless_air_marshal` - Get Air Marshal results

### Appliance (11 tools)
- `appliance_vlans_list` - List VLANs
- `appliance_vlan_create` - Create VLAN
- `appliance_firewall_l3_rules_get` - Get firewall rules
- `appliance_firewall_l3_rules_update` - Update firewall rules
- `appliance_vpn_settings_get` - Get VPN settings
- `appliance_vpn_settings_update` - Update VPN settings
- `appliance_one_to_one_nat_rules_get` - Get 1:1 NAT rules
- `appliance_one_to_one_nat_rules_update` - Update 1:1 NAT rules
- `appliance_port_forwarding_rules_get` - Get port forwarding rules
- `appliance_port_forwarding_rules_update` - Update port forwarding rules
- `appliance_traffic_shaping_get` - Get traffic shaping rules

### Monitoring (7 tools)
- `monitoring_uplinks_status` - Get uplink status
- `monitoring_connection_stats` - Get connection statistics
- `monitoring_latency_stats` - Get latency statistics
- `monitoring_events` - Get event log
- `monitoring_client_health` - Get client health
- `monitoring_device_performance` - Get device performance
- `monitoring_network_traffic` - Get traffic analysis

### Alerts (7 tools)
- `alerts_settings_get` - Get alert settings
- `alerts_settings_update` - Update alert settings
- `webhooks_list` - List webhooks
- `webhook_create` - Create webhook
- `webhook_update` - Update webhook
- `webhook_delete` - Delete webhook
- `webhook_test` - Test webhook

### Camera (10 tools)
- `camera_quality_get` - Get quality settings
- `camera_quality_update` - Update quality settings
- `camera_video_settings_get` - Get video settings
- `camera_video_settings_update` - Update video settings
- `camera_snapshot` - Generate snapshot
- `camera_video_link` - Get video link
- `camera_zones_get` - Get detection zones
- `camera_sense_get` - Get MV Sense settings
- `camera_sense_update` - Update MV Sense settings
- `camera_analytics_overview` - Get analytics overview

**Total: 79 tools**

## Architecture```
mcp-meraki/
├── src/
│   ├── index.ts              # Main MCP server
│   ├── meraki-client.ts      # HTTP client with rate limiting
│   ├── types.ts              # TypeScript type definitions
│   ├── utils.ts              # Utilities (retry, pagination, cache)
│   └── tools/
│       ├── organizations.ts  # Organization tools
│       ├── networks.ts       # Network tools
│       ├── devices.ts        # Device tools
│       ├── switch.ts         # Switch tools
│       ├── wireless.ts       # Wireless tools
│       ├── appliance.ts      # Appliance tools
│       ├── monitoring.ts     # Monitoring tools
│       ├── alerts.ts         # Alert/webhook tools
│       └── camera.ts         # Camera tools
├── dist/                     # Compiled JavaScript
├── package.json
├── tsconfig.json
├── .env                      # Environment variables (create from .env.example)
└── README.md

Development

Scripts```bash

Build the project

npm run build

Watch mode (rebuild on changes)

npm run dev

Run the server

npm start


### Adding New Tools

1. Add type definitions to `src/types.ts`
2. Create tool definition and handler in appropriate `src/tools/*.ts` file
3. Export tool and handler from the file
4. Tools are automatically registered in `src/index.ts`

### Debugging

Enable debug logging by setting `DEBUG=true` in your `.env` file or environment:```bash
DEBUG=true npm start

Rate Limiting

The server respects Meraki's API rate limits:
- Default: 5 requests per second per organization
- Configurable via MERAKI_RATE_LIMIT environment variable
- Automatic retry with exponential backoff on rate limit errors (429)
- Automatic retry on server errors (5xx)

Error Handling

All errors are formatted consistently:json { "error": true, "tool": "networks_get", "status": 404, "statusText": "Not Found", "message": "Network not found", "errors": ["Network L_123456789 not found"], "endpoint": "/networks/L_123456789" }

Security Best Practices

  1. Never commit .env file - It contains your API key
  2. Use read-only API keys when possible
  3. Restrict API key to specific organizations in Dashboard
  4. Enable IP restrictions on your API key if deploying to servers
  5. Rotate API keys regularly

Troubleshooting

Server not appearing in Claude

  1. Check Claude Desktop logs: ~/Library/Logs/Claude/mcp*.log
  2. Verify absolute path in config is correct
  3. Ensure project is built: npm run build
  4. Check Node.js version: node --version (requires 18+)

Authentication errors

  1. Verify API key is correct in .env
  2. Check API key is enabled in Dashboard
  3. Ensure API key has access to the organization

Rate limiting

  1. Reduce MERAKI_RATE_LIMIT if hitting limits
  2. Check for concurrent requests
  3. Review API usage: organizations_api_requests

Resources

  • Meraki Dashboard API Documentation
  • Model Context Protocol Documentation
  • Get Meraki API Key

License

MIT

Contributing

Contributions are welcome! Please feel free to submit issues or pull requests.

Acknowledgments

Built with:
- Model Context Protocol SDK
- Axios
- TypeScript

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
mcp-meraki 怎么安装?

在客户端按下面的安装命令接入:node /absolute/path/to/mcp-meraki/dist/index.js。装完在客户端配置里引用同一个包或端点。

mcp-meraki 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

mcp-meraki 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

mcp-meraki 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

mcp-meraki 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

mcp-meraki 能提供哪些能力?

资料显示能力标签包括 Local Deployment、Network Management、API Integration、TypeScript、Device Control、Monitoring Tool。具体工具清单以官方文档为准。

mcp-meraki 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

mcp-meraki 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-10-06。