About Splunk Meraki
Splunk Meraki is an MCP server published by kiskander in the Developer Tools category: self-Healing Networks with Splunk MCP and custom Meraki MCP.
The repository has 16 stars and 11 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/kiskander/mcp-splunk-merakiThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Splunk Meraki
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 16 hours ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- !Dependencies pinnedNo lockfile. Installs can pull different code over time.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
🧠 Self-Healing Network with MCP Agents
This repository demonstrates how to build agentic workflows using two MCP servers to detect and reverse configuration drift in a Meraki network. The system utilizes:
- A Splunk MCP Agent to detect network changes. Credit to William Searle for the Splunk MCP Server.
- A Meraki MCP Agent to reverse unauthorized changes.
Agentic AI handles both detection and remediation based on natural language prompts—no hardcoded orchestration required.
🚀 How It Works
- You ask: “What changed in my Meraki network?”
- The Splunk MCP Agent queries Splunk using its SDK and returns configuration drift.
- The Meraki MCP Agent compares the change to the source of truth and calls the appropriate Meraki API to reverse it.
🛠️ Prerequisites
- Python 3.10 or higher
- Access to:
- A Splunk instance with relevant logs
- A Meraki Dashboard API key
- Claude Desktop or any MCP-compatible client
claude_desktop_config.jsonconfigured with correct tool registration and MCP server paths
📦 Installation
Clone the repository:
git clone https://github.com/kiskander/mcp-splunk-meraki.git
cd mcp-splunk-meraki
Splunk MCP Setup (Local Installation)
for more Splunk MCP installation options checkout: https://github.com/livehybrid/splunk-mcp
-
Access Splunk MCP:
cd mcp-splunk-meraki/SplunkMCP -
Install dependencies using Poetry:
poetry install -
Configure environment variables:
Copy the example environment file and update it with your Splunk credentials:
cp .env.example .envUpdate the
.envfile with the following:SPLUNK_HOST=your_splunk_host SPLUNK_PORT=8089 SPLUNK_USERNAME=your_username SPLUNK_PASSWORD=your_password SPLUNK_SCHEME=https VERIFY_SSL=true FASTMCP_LOG_LEVEL=INFO SERVER_MODE=stdio -
Run the Splunk MCP:
poetry run python splunk_mcp.py stdio
Meraki MCP Setup
-
Install
uv(if not already installed):For macOS/Linux:
brew install uv -
Set Up Your Meraki MCP Project:
cd mcp-splunk-meraki/MerakiMCP -
Install dependencies using
uv:uv init uv venv source .venv/bin/activate # or .venv\Scripts\activate on Windows uv add "mcp[cli]" uv add "meraki" -
Run the Meraki MCP Agent:
python meraki_mcp.py
README fetched from the repository 16 hours ago. The original is authoritative.