> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myrmex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cisco Meraki

> Connect a Cisco Meraki security appliance (MX) to Myrmex with a Dashboard API key — create the key and add the integration.

import { Note, Steps, Step, CardGroup, Card, Tip } from '@mintlify/components';

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](/documentation/agent-endpoint-security/collector-mode) on your network, querying it in real time.

## What Myrmex Can Do

<CardGroup cols={2}>
  <Card title="Read & troubleshoot" icon="magnifying-glass">
    Query the appliance, its networks, and security settings on demand — read-only diagnostics.
  </Card>

  <Card title="Hardening audit" icon="shield-halved">
    Run a [Security Posture](/documentation/security-posture/overview) audit against the appliance configuration.
  </Card>

  <Card title="Policy review" icon="broom">
    Review firewall and content-filtering rules and propose cleanups.
  </Card>

  <Card title="Change on approval" icon="floppy-disk">
    Apply configuration changes through the Dashboard API, with your approval.
  </Card>
</CardGroup>

## Before You Start

* A **Collector** that can reach the Meraki Dashboard API (`api.meraki.com`) over HTTPS. See [Deploying the agent](/documentation/agent-endpoint-security/installation).
* **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.

<Steps>
  <Step title="Enable API access">
    In the Meraki Dashboard, go to **Organization → Settings** and enable **Dashboard API access**.
  </Step>

  <Step title="Generate the API key">
    Open **My Profile → API access** and **Generate API key**. Copy it now — it is shown only once.
  </Step>

  <Step title="Collect the IDs">
    Note your **Organization ID**, the appliance's **Network ID**, and the MX **serial** (available from the dashboard or the Dashboard API).
  </Step>
</Steps>

<Tip>
  The API key inherits the creating account's permissions — use an account scoped to just what Myrmex should do.
</Tip>

## Step 2 — Add the Integration in Myrmex

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

| Field               | Description                                                                                               |
| ------------------- | --------------------------------------------------------------------------------------------------------- |
| **Name**            | A unique name for this Meraki appliance.                                                                  |
| **Description**     | Optional note to identify the device.                                                                     |
| **API Key**         | The Meraki Dashboard API key from Step 1.                                                                 |
| **Organization ID** | The Meraki organization that owns the appliance.                                                          |
| **Network ID**      | The network the appliance belongs to.                                                                     |
| **Serial**          | The MX appliance serial number.                                                                           |
| **Collector**       | The [Collector](/documentation/agent-endpoint-security/collector-mode) that will reach the Dashboard API. |
| **Protocol**        | Protocol used for the API (default `https`).                                                              |
| **API Host**        | The Dashboard API host (default `api.meraki.com`).                                                        |
| **API Port**        | The API port (default `443`).                                                                             |
| **Auth Type**       | Authentication method (preset to `bearer`).                                                               |
| **Version**         | Optional. The appliance firmware version.                                                                 |
| **Model**           | Optional. The MX appliance model.                                                                         |

## Connect

Click **Connect** to validate the API key and finish. The Meraki appliance then appears under **Environment → Integrations**, and you can start asking [Hydra](/documentation/multi-agent-system/integration-specialist-agent) about it in the Workspace.

<Note>
  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.
</Note>