Skip to main content
Connect your Cisco Meraki security appliance (MX) so Myrmex can read its configuration, review its security services, and — with approval — help you manage it. Myrmex reaches the Meraki Dashboard API (api.meraki.com) through a Collector on your network, querying it in real time.

​
What Myrmex Can Do

Read & troubleshoot

Query the appliance, its networks, and security settings on demand — read-only diagnostics.

Hardening audit

Run a Security Posture audit against the appliance configuration.

Policy review

Review firewall and content-filtering rules and propose cleanups.

Change on approval

Apply configuration changes through the Dashboard API, with your approval.

​
Before You Start

  • A Collector that can reach the Meraki Dashboard API (api.meraki.com) over HTTPS. See Deploying the agent.
  • API access enabled for your organization in the Meraki Dashboard.
  • Your Organization ID and the Network ID of the appliance.

​
Step 1 — Create the API Key in Meraki

The credential Myrmex needs is a Dashboard API key, used as a Bearer token. The key inherits the dashboard permissions of the account that creates it.
1

Enable API access

In the Meraki Dashboard, go to Organization → Settings and enable Dashboard API access.
2

Generate the API key

Open My Profile → API access and Generate API key. Copy it now — it is shown only once.
3

Collect the IDs

Note your Organization ID, the appliance’s Network ID, and the MX serial (available from the dashboard or the Dashboard API).
The API key inherits the creating account’s permissions — use an account scoped to just what Myrmex should do.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Meraki Appliance, then fill in:

​
Connect

Click Connect to validate the API key and finish. The Meraki appliance then appears under Environment → Integrations, and you can start asking Hydra about it in the Workspace.
Your API key is stored securely and resolved server-side — it never passes through the AI, and Myrmex queries Meraki on demand rather than storing its data.