Meraki Wireless (BYOK)

Meraki Wireless (BYOK) — connector documentation

• MCP endpoint: https://byok-meraki-wireless.connectorbay.com/mcp
• REST API: POST https://byok-meraki-wireless.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-meraki-wireless.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Meraki Wireless 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-wireless.connectorbay.com/health · Tool schemas: https://byok-meraki-wireless.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-meraki-wireless · agent@connectorbay.com

What Meraki Wireless (BYOK) is for

Meraki Wireless (BYOK) lets an AI assistant read your own Meraki Wireless data through the Meraki Wireless API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 7 tools (get_channel_utilization_by_device, get_channel_utilization_by_network, get_packet_loss_by_device, get_packet_loss_by_network, list_ethernet_statuses, get_client_counts_by_device, list_bssid_statuses). 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 Meraki Wireless. Meraki Wireless 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 of my Meraki access points have congested channels?"
• "How busy is the Wi-Fi in each of my Meraki networks?"
• "Which Meraki access points lose the most packets?"
• "What is the Wi-Fi packet loss in each of my Meraki networks?"
• "Are my Meraki access points getting enough PoE power?"
• "How many clients are connected to each of my Meraki access points?"

What it does

• get_channel_utilization_by_device: Get average channel utilization per access point and radio band over a window, bucketed by an interval.
• get_channel_utilization_by_network: Get average channel utilization per network and radio band over a window.
• get_packet_loss_by_device: Get average downstream and upstream packet loss per access point over a window, optionally for one band or SSID number.
• get_packet_loss_by_network: Get average downstream and upstream packet loss per network over a window, optionally for one band or SSID number.
• list_ethernet_statuses: List the latest Ethernet status of access points: power mode and draw, ports with link speed and duplex, and link aggregation.
• get_client_counts_by_device: Get the number of wireless clients currently connected to each access point (counts only, no client details).
• list_bssid_statuses: List the status of every BSSID per access point: device name, serial, network and the SSID broadcast details by band and channel.

BYOK key

You bring your own Meraki Wireless 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 Meraki Wireless 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 Meraki Wireless. Meraki Wireless 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 Meraki Wireless account.

Built for: Worldwide. Languages: English.

Meraki Wireless (BYOK) — Privacy Policy

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

What Meraki Wireless (BYOK) is. Meraki Wireless (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Wireless data: Read access point channel utilization, packet loss, Ethernet status, client counts and BSSID status of your Cisco Meraki wireless network with your own Dashboard API key. You bring your own Meraki Wireless 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 Meraki Wireless 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 Meraki Wireless 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 Meraki Wireless receives. The request we make on your behalf, including the key and the arguments, under Meraki Wireless's own terms and privacy policy. Meraki Wireless acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Meraki Wireless 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 Meraki Wireless 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. Meraki Wireless (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 Meraki Wireless at any time to end all access.

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

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

Meraki Wireless (BYOK) — Terms of Service

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

1. The Service. Meraki Wireless (BYOK) provides: Read access point channel utilization, packet loss, Ethernet status, client counts and BSSID status of your Cisco Meraki wireless network 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 Meraki Wireless credentials and only access data you are allowed to access. Meraki Wireless's terms apply to your use of Meraki Wireless; 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 Meraki Wireless. Meraki Wireless 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 Meraki Wireless returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Wireless. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Wireless 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 Meraki Wireless'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; Meraki Wireless 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 Meraki Wireless 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 Meraki Wireless 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-wireless

Meraki Wireless (BYOK) support

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

• MCP endpoint: https://byok-meraki-wireless.connectorbay.com/mcp
• REST API: https://byok-meraki-wireless.connectorbay.com/openapi.json
• Live status: https://byok-meraki-wireless.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. Meraki Wireless (BYOK) never asks for them.