Meraki Device Diagnostics (BYOK)

Meraki Device Diagnostics (BYOK) — connector documentation

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

What Meraki Device Diagnostics (BYOK) is for

Meraki Device Diagnostics (BYOK) lets an AI assistant read your own Meraki Device Diagnostics data through the Meraki Device Diagnostics API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 8 tools (get_lldp_cdp, get_loss_and_latency_history, list_device_switch_port_statuses, list_device_switch_port_packets, get_access_point_status, get_access_point_connection_stats, get_access_point_latency_stats, get_appliance_performance). 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 Device Diagnostics. Meraki Device Diagnostics 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:

• "What neighbors does Meraki device Q2XX-XXXX-XXXX see over LLDP or CDP?"
• "What was the latency from Meraki appliance Q2XX-XXXX-XXXX to 8.8.8.8 yesterday?"
• "Which ports on Meraki switch Q2XX-XXXX-XXXX are connected and at what speed?"
• "How many packets did each port of Meraki switch Q2XX-XXXX-XXXX carry?"
• "Which SSIDs and channels is Meraki access point Q2XX-XXXX-XXXX using?"
• "How many Wi-Fi connections failed at Meraki access point Q2XX-XXXX-XXXX?"

What it does

• get_lldp_cdp: Get the LLDP and CDP neighbor information a device has seen on each of its ports, with the device's source MAC.
• get_loss_and_latency_history: Get the uplink packet loss, latency, jitter and goodput of an appliance towards a destination IP over time. The destination ip is required.
• list_device_switch_port_statuses: List the status of every port of one switch: link state, speed, duplex, uplink flag, errors, warnings, PoE allocation and traffic in kilobytes.
• list_device_switch_port_packets: List the packet counters (by type, with rates) of every port of one switch over a period.
• get_access_point_status: Get the SSID and BSSID status of one access point: SSID name and number, enabled, band, BSSID, channel, width, power, visibility and broadcast state.
• get_access_point_connection_stats: Get aggregated client connection results of one access point over a period: association, authentication, DHCP, DNS failures and successes.
• get_access_point_latency_stats: Get aggregated wireless latency of one access point per traffic class (background, best effort, video, voice) over a period.
• get_appliance_performance: Get the performance score of one MX appliance or Secure Router over a period (device utilization as a number).

BYOK key

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

Built for: Worldwide. Languages: English.

Meraki Device Diagnostics (BYOK) — Privacy Policy

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

What Meraki Device Diagnostics (BYOK) is. Meraki Device Diagnostics (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Device Diagnostics data: Read per-device diagnostics of your Cisco Meraki hardware by serial: LLDP/CDP neighbors, WAN loss and latency, switch port status, AP radio status and appliance performance. You bring your own Meraki Device Diagnostics 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 Device Diagnostics 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 Device Diagnostics 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 Device Diagnostics receives. The request we make on your behalf, including the key and the arguments, under Meraki Device Diagnostics's own terms and privacy policy. Meraki Device Diagnostics 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 Device Diagnostics 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 Device Diagnostics 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 Device Diagnostics (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 Device Diagnostics at any time to end all access.

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

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

Meraki Device Diagnostics (BYOK) — Terms of Service

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

1. The Service. Meraki Device Diagnostics (BYOK) provides: Read per-device diagnostics of your Cisco Meraki hardware by serial: LLDP/CDP neighbors, WAN loss and latency, switch port status, AP radio status and appliance performance. 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 Device Diagnostics credentials and only access data you are allowed to access. Meraki Device Diagnostics's terms apply to your use of Meraki Device Diagnostics; 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 Device Diagnostics. Meraki Device Diagnostics 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 Device Diagnostics returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Device Diagnostics. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Device Diagnostics 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 Device Diagnostics'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 Device Diagnostics 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 Device Diagnostics 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 Device Diagnostics 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-device-diagnostics

Meraki Device Diagnostics (BYOK) support

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

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