How to Use the Cisco Meraki MCP in CrewAI

Q: How do I connect the Cisco Meraki MCP Server to CrewAI?

Pass the Vinkius URL directly into the mcps list when defining your agent. For more granular control, import MCPServerHTTP from crewai.mcp and configure the transport manually.

Q: How do I limit which Cisco Meraki tools a CrewAI agent can use?

Use the toolfilter argument during setup. You can restrict an agent so it only has access to client listing operations, keeping it away from core appliance settings.

Deploy autonomous agent squads to monitor and analyze your Cisco Meraki networks using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cisco Meraki MCP to CrewAI

Create your Vinkius account to connect Cisco Meraki to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Cisco Meraki with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Network Monitoring

A single script can't handle complex infrastructure troubleshooting. CrewAI lets you assign a dedicated Watcher agent to poll `get_device_statuses` across your entire organization. This agent does nothing but look for offline access points or struggling switches. When the Watcher finds a problem, it passes the context to a Diagnostics agent in shared memory. The second agent immediately runs `get_appliance_settings` and `get_device` to gather firmware details and routing configurations. The squad collaborates to figure out why the hardware failed before a human even opens a ticket.

Fleet-Wide Wireless Audits

Auditing guest networks across fifty retail locations takes days of manual work. You can spin up a specialized CrewAI researcher to map every deployment by calling `list_networks` followed by `list_wireless_ssids`. The agent systematically documents the authentication type and broadcast status for every single location. A secondary security agent takes that mapped data and looks for active threats. It hits `list_clients` on any open network to check for unusual device counts or strange MAC address patterns. The crew compiles a final markdown report detailing exactly which sites need configuration updates.

Hierarchical MCP Server Access

Giving every AI agent full access to your cloud dashboard is a bad idea. You can use the `tool_filter` in your Python setup to restrict who sees what. The junior reporting agent only gets permission to run `list_organizations` and `search_organizations` to build directories. The senior manager agent holds the keys to the deeper appliance settings. You pass the Vinkius endpoint directly into the `mcps` array for that specific role. This ensures your autonomous operations follow strict least-privilege rules while still getting the job done.

Setup guide

Set up Cisco Meraki MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Cisco Meraki tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cisco Meraki Analyst",
    goal="Access and analyze Cisco Meraki data via MCP.",
    backstory="Expert analyst with direct Cisco Meraki access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Cisco Meraki transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Cisco Meraki Analyst",
        goal="Access and analyze Cisco Meraki data via MCP.",
        backstory="Expert analyst with direct Cisco Meraki access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Cisco Meraki transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cisco Meraki. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Cisco Meraki now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Cisco Meraki MCP in CrewAI

Pass the Vinkius URL directly into the `mcps` list when defining your agent. For more granular control, import `MCPServerHTTP` from `crewai.mcp` and configure the transport manually.

Yes. The framework uses shared memory to pass context between roles. If Agent A finds an offline switch, Agent B can read that exact MAC address from memory and query its configuration without asking the API twice.

Use the `tool_filter` argument during setup. You can restrict an agent so it only has access to client listing operations, keeping it away from core appliance settings.

The agent logs the failure and attempts to use alternative tools if available. You can also configure a manager agent to review the error and instruct the crew to try searching by a different organization ID.

Your network topology remains strictly confidential. The integration reads internal IP schemas, connected client MAC addresses, and switch firmware versions via a Vinkius V8 Isolate. The sandbox executes the API call and immediately self-destructs, leaving zero persistent data behind.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript