Cisco Meraki (BYOK)

Cisco Meraki (BYOK) — connector documentation

• MCP endpoint: https://byok-meraki.connectorbay.com/mcp
• REST API: POST https://byok-meraki.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-meraki.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Cisco Meraki Meraki Dashboard API key (Organization > API & Webhooks), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-meraki.connectorbay.com/health · Tool schemas: https://byok-meraki.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-meraki · agent@connectorbay.com

What Cisco Meraki (BYOK) is for

Cisco Meraki (BYOK) lets an AI assistant read your own Cisco Meraki data through the Cisco Meraki API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 12 tools (list_organizations, list_networks, list_organization_devices, list_device_statuses, get_device_status_overview, list_network_devices, get_device, list_network_clients, list_network_events, get_license_overview, list_organization_admins, list_inventory_devices). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.meraki.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cisco Meraki. Cisco Meraki and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Meraki organizations can my API key see?"
• "What Meraki networks does organization 549236 have?"
• "Which Meraki access points and switches are in my organization?"
• "Which Meraki devices are offline right now?"
• "How many of my Meraki devices are online versus offline?"
• "What devices are in Meraki network L_646829496481105433?"

What it does

• list_organizations: List the Meraki organizations the key can access with id, name, dashboard URL, licensing model and cloud region.
• list_networks: List the networks of an organization with name, product types, time zone, tags and dashboard URL.
• list_organization_devices: List the devices assigned to networks in an organization with name, serial, model, MAC, LAN IP, firmware and tags. Optional filters match part of the name, model, serial or MAC.
• list_device_statuses: List the current status (online, alerting, offline or dormant) of every device in an organization with last report time, public and LAN IP, model and tags.
• get_device_status_overview: Count the devices of an organization by status: online, alerting, offline and dormant.
• list_network_devices: List the devices in one network with name, serial, model, MAC, LAN IP, firmware, address and tags.
• get_device: Get one Meraki device by serial number: name, model, MAC, LAN IP, firmware, network, address, notes, tags and coordinates.
• list_network_clients: List clients seen on a network in a time span (up to 31 days) with MAC, IP, description, OS, VLAN, SSID or switch port, status and data usage (sent and received). Optional partial-match filters.
• list_network_events: List recent events of a network (client connections, device changes, VPN and firewall events) with time, type, description, device and client. Networks with several product types need product_type.
• get_license_overview: Show the license state of an organization: status, expiration date, license count and how many licenses are active, expiring or expired.
• list_organization_admins: List the dashboard administrators of an organization with name, email, access level, account status, two-factor and API key flags and last activity.
• list_inventory_devices: List the device inventory of an organization, including unclaimed-to-network devices, with serial, model, order number, claim date, license expiry and end-of-life status.

BYOK key

You bring your own Cisco Meraki Meraki Dashboard API key (Organization > API & Webhooks) (https://dashboard.meraki.com/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.meraki.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.cisco.com/meraki/api-v1/ (the API this connector calls, with a BYOK key)

Live from the Cisco Meraki API (api.meraki.com) with a BYOK key; documentation: https://developer.cisco.com/meraki/api-v1/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cisco Meraki. Cisco Meraki and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Cisco Meraki account.

Built for: Worldwide. Languages: English.

Cisco Meraki (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Cisco Meraki (BYOK) is. Cisco Meraki (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Cisco Meraki data: Read your Cisco Meraki organizations, networks, devices, device status, clients, events, licenses and admins with your own Dashboard API key. You bring your own Cisco Meraki Meraki Dashboard API key (Organization > API & Webhooks); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Cisco Meraki call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.meraki.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Cisco Meraki rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Cisco Meraki receives. The request we make on your behalf, including the key and the arguments, under Cisco Meraki's own terms and privacy policy. Cisco Meraki acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Cisco Meraki gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Cisco Meraki data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Cisco Meraki (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Cisco Meraki at any time to end all access.

Children. Cisco Meraki (BYOK) is a general-audience service operated by the adult using the assistant, under Cisco Meraki's own age rules.

Changes. We will post changes here with a new effective date.

Cisco Meraki (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Cisco Meraki (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Cisco Meraki (BYOK) provides: Read your Cisco Meraki organizations, networks, devices, device status, clients, events, licenses and admins with your own Dashboard API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Cisco Meraki credentials and only access data you are allowed to access. Cisco Meraki's terms apply to your use of Cisco Meraki; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cisco Meraki. Cisco Meraki and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Cisco Meraki returns, lightly trimmed; it may be incomplete, delayed or changed by Cisco Meraki. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Cisco Meraki account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Cisco Meraki's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Cisco Meraki may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Cisco Meraki key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Cisco Meraki takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-meraki

Cisco Meraki (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-meraki.connectorbay.com/mcp
• REST API: https://byok-meraki.connectorbay.com/openapi.json
• Live status: https://byok-meraki.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Cisco Meraki (BYOK) never asks for them.