Meraki MCP Ebed7041

MCP运维云端

提供方 cap5192

运维云端 stdio · 本地进程 无需鉴权 社区 / 第三方
查看接入方式

一个提供与Cisco Meraki Dashboard API交互工具的MCP服务器,支持大规模程序化管理和监控Meraki网络。

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

适用场景

网络管理Python本地部署API工具云网络设备监控Meraki

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
pip install mcp httpx pydantic --break-system-packages

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

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 8 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

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

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

部署与发布

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

监控与告警

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

选择建议

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

值得选的地方

  • 资料标注 8 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Meraki MCP Ebed7041当前 8 stdio · 本地进程 本地部署 有 2026-05-17
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

服务器档案

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

详细介绍

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

Cisco Meraki MCP Server

A Model Context Protocol (MCP) server that provides tools to interact with the Cisco Meraki Dashboard API, enabling programmatic management and monitoring of Meraki networks at scale.

Overview

This MCP server allows AI assistants to manage and monitor Cisco Meraki cloud-managed networks through the Meraki Dashboard API. It provides tools for:

  • Organization Management: List and access Meraki organizations
  • Network Management: List and manage networks within organizations
  • Device Management: Monitor and manage network devices (access points, switches, security appliances)
  • Client Monitoring: Track connected clients and their usage
  • Uplink Monitoring: Monitor WAN connections and uplink health

Features

  • ✅ Read-Only Operations: Safe monitoring and reporting without modifying configurations
  • ✅ Multiple Response Formats: Support for both Markdown (human-readable) and JSON (machine-readable)
  • ✅ Comprehensive Error Handling: Clear, actionable error messages for troubleshooting
  • ✅ Filtering Support: Filter devices by product type, network, tags, and status
  • ✅ Pagination Ready: Handles large datasets with truncation and guidance
  • ✅ Rate Limit Aware: Includes handling for Meraki's API rate limits (10 req/sec per org)

Prerequisites

  • Python 3.10 or higher
  • Cisco Meraki Dashboard account with API access
  • Meraki API key

Installation

  1. Install the MCP Python SDK:```bash
    pip install mcp httpx pydantic --break-system-packages

2. **Set your Meraki API key as an environment variable**:```bash
export MERAKI_API_KEY="your_api_key_here"

To get your Meraki API key:
1. Log into the Meraki Dashboard
2. Navigate to Organization → Configure → API & Webhooks
3. Click "Generate API Key" under the "API keys and access" tab
4. Copy the generated API key

⚠️ Security Note: Never commit your API key to version control. Always use environment variables.

Usage

Running the Server

Run the MCP server using the mcp command:```bash
mcp run meraki_mcp.py


Or execute it directly:```bash
python meraki_mcp.py

Available Tools

1. meraki_list_organizations

List all Meraki organizations accessible by your API key.

Use cases:
- Find your organization ID for other API calls
- List all organizations you manage
- Get organization details for reporting

Example:```
List all my Meraki organizations


#### 2. **meraki_list_networks**
List all networks within a specific organization.

**Parameters**:
- `organization_id`: The organization ID to query
- `response_format`: Output format (markdown or json)

**Use cases**:
- Find network IDs for device management
- List all networks in an organization
- Check which product types each network supports

**Example**:```
List all networks in organization 549236

3. meraki_get_network

Get detailed information about a specific network.

Parameters:
- network_id: The network ID to retrieve
- response_format: Output format (markdown or json)

Use cases:
- Get network configuration details
- Check enabled product types
- Verify network settings

Example:```
Get details for network N_24329156


#### 4. **meraki_list_devices**
List all devices in an organization with optional filtering.

**Parameters**:
- `organization_id`: The organization ID
- `product_types`: Optional filter by device types (wireless, switch, appliance, etc.)
- `network_ids`: Optional filter by network IDs
- `tags`: Optional filter by device tags
- `response_format`: Output format (markdown or json)

**Use cases**:
- List all wireless access points
- Find devices in a specific network
- Get device inventory for reporting
- Locate devices with specific tags

**Example**:```
List all wireless devices in organization 549236
Show me switches in network N_24329156

5. meraki_get_device_statuses

Get real-time status of devices in an organization.

Parameters:
- organization_id: The organization ID
- statuses: Optional filter by status (online, offline, alerting, dormant)
- product_types: Optional filter by product types
- network_ids: Optional filter by network IDs
- response_format: Output format (markdown or json)

Use cases:
- Monitor which devices are online or offline
- Check for alerting devices needing attention
- Get real-time network health overview
- Troubleshoot connectivity issues

Example:```
Show me all offline devices in organization 549236
Which devices are alerting?


#### 6. **meraki_get_device**
Get detailed information about a specific device.

**Parameters**:
- `serial`: The device serial number
- `response_format`: Output format (markdown or json)

**Use cases**:
- Get device configuration details
- Check device firmware version
- Verify device network assignment
- Get device location information

**Example**:```
Get details for device Q234-ABCD-5678

7. meraki_list_network_clients

List clients connected to a network within a specified timespan.

Parameters:
- network_id: The network ID
- timespan: Timespan in seconds (default 86400 = 1 day, max 2592000 = 30 days)
- response_format: Output format (markdown or json)

Use cases:
- Monitor connected devices
- Track client data usage
- Identify unauthorized devices
- Analyze network utilization

Example:```
Show me clients connected to network N_24329156 in the last 24 hours
List all clients from the past week


#### 8. **meraki_get_organization_uplinks_statuses**
Get uplink status of all devices in an organization.

**Parameters**:
- `organization_id`: The organization ID
- `network_ids`: Optional filter by network IDs
- `response_format`: Output format (markdown or json)

**Use cases**:
- Monitor WAN connectivity across organization
- Check uplink failover status
- Identify connectivity issues
- Track public IP assignments

**Example**:```
Show me uplink status for all devices in organization 549236
Check WAN connectivity for organization

Configuration

Environment Variables

  • MERAKI_API_KEY (required): Your Meraki Dashboard API key

API Rate Limits

The Meraki Dashboard API has a rate limit of 10 requests per second per organization. The server includes error handling for rate limit errors (HTTP 429) and will provide guidance when limits are exceeded.

Response Formats

Markdown Format (Default)

Human-readable format with:
- Headers and sections for easy scanning
- Bullet points for key information
- Formatted timestamps
- Grouped related data

JSON Format

Machine-readable format with:
- Complete structured data
- All available fields
- Consistent field names
- Suitable for programmatic processing

Error Handling

The server provides clear, actionable error messages for common issues:

  • 400 Bad Request: Invalid parameters - check your input
  • 401 Unauthorized: Invalid API key - verify MERAKI_API_KEY environment variable
  • 403 Forbidden: No permission - check API key organization access
  • 404 Not Found: Resource doesn't exist - verify IDs are correct
  • 429 Rate Limit: Too many requests - wait before retrying (10 req/sec limit)
  • Timeout: Request took too long - retry or check network connection

Architecture

Tool Organization

Tools are organized by resource type:
- Organization Tools: List and manage organizations
- Network Tools: Manage networks and configurations
- Device Tools: Monitor and manage devices
- Client Tools: Track connected clients
- Uplink Tools: Monitor WAN connectivity

Design Principles

  1. Read-Only First: All tools are read-only to ensure safety
  2. Consistent Naming: Tools follow meraki_{action}_{resource} pattern
  3. Flexible Filtering: Support for multiple filter parameters
  4. Response Format Options: Both human and machine-readable formats
  5. Error Clarity: Actionable error messages with remediation guidance

Development

Project Structure```

meraki_mcp/
├── meraki_mcp.py # Main server implementation
├── README.md # This file
└── requirements.txt # Python dependencies (optional)


### Adding New Tools

To add new tools:

1. Define a Pydantic input model with validation
2. Use the `@mcp.tool()` decorator with appropriate annotations
3. Implement the tool function with comprehensive docstring
4. Add error handling with `_handle_api_error()`
5. Support both response formats (markdown and json)
6. Include truncation for large responses

### Testing

Test the server with the MCP inspector:```bash
npx @modelcontextprotocol/inspector python meraki_mcp.py

Or test individual tools:```python

Set environment variable

export MERAKI_API_KEY="your_key"

Run server

python meraki_mcp.py
```

Meraki API Resources

  • Meraki Developer Hub
  • Dashboard API Documentation
  • Getting Started Guide
  • Postman Collection
  • Python SDK

License

This MCP server is provided as-is for use with the Cisco Meraki Dashboard API. Please refer to Cisco's API terms of service and licensing agreements.

Support

For issues related to:
- MCP Server: Check error messages and this README
- Meraki API: Visit Meraki Developer Community
- API Keys: Contact your Meraki administrator or Cisco support

Changelog

Version 1.0.0

  • Initial release with 8 core tools
  • Organization, network, and device management
  • Client monitoring and uplink status tracking
  • Markdown and JSON response formats
  • Comprehensive error handling

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Meraki MCP Ebed7041 怎么安装?

在客户端按下面的安装命令接入:pip install mcp httpx pydantic --break-system-packages。装完在客户端配置里引用同一个包或端点。

Meraki MCP Ebed7041 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Meraki MCP Ebed7041 收费吗?

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

Meraki MCP Ebed7041 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Meraki MCP Ebed7041 能提供哪些能力?

资料显示约 8 个工具;能力标签包括 网络管理、Python、API集成。具体工具清单以官方文档为准。

Meraki MCP Ebed7041 需要什么运行环境?

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

Meraki MCP Ebed7041 是本地还是远程?

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

热门专题

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

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