Meraki Appliances (BYOK)

Meraki Appliances (BYOK) — connector documentation

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

What Meraki Appliances (BYOK) is for

Meraki Appliances (BYOK) lets an AI assistant read your own Meraki Appliances data through the Meraki Appliances API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 7 tools (list_uplink_statuses, get_uplink_status_overview, list_vpn_statuses, list_vpn_stats, get_uplink_usage_by_network, list_l3_interfaces, list_intrusion_policy_overviews). 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 Appliances. Meraki Appliances 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 MX appliances have a failed WAN uplink?"
• "How many Meraki MX uplinks are active versus failed?"
• "Which of my Meraki site-to-site VPN tunnels are unreachable?"
• "How was the latency of my Meraki VPN tunnels over the last day?"
• "How much data did each Meraki network send over its WAN uplinks last week?"
• "What L3 interfaces do my Meraki MX appliances have?"

What it does

• list_uplink_statuses: List the uplink status of each MX appliance, Z-series teleworker gateway and Secure Router in an organization: model, last report time, high-availability role and the uplinks with interface, status, IP and provider.
• get_uplink_status_overview: Count the MX uplinks of an organization by status: active, ready, failed, connecting and not connected.
• list_vpn_statuses: Show the site-to-site VPN status per network: appliance serial and status, VPN mode, uplinks, exported subnets and the Meraki and third-party VPN peers with reachability.
• list_vpn_stats: Show VPN history statistics per network over a period: for each Meraki VPN peer the loss, latency, jitter and mean opinion score per uplink pair.
• get_uplink_usage_by_network: Get the bytes sent and received on each MX or Z-series uplink per network over a period.
• list_l3_interfaces: List the layer 3 interfaces configured on MX appliances across networks of an organization: interface id, IPv4 settings, network and port.
• list_intrusion_policy_overviews: List the intrusion prevention and base policies of an organization with the counts of networks and rules that use each.

BYOK key

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

Built for: Worldwide. Languages: English.

Meraki Appliances (BYOK) — Privacy Policy

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

What Meraki Appliances (BYOK) is. Meraki Appliances (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Appliances data: Read the uplink status, VPN health, uplink usage and L3 interfaces of your Cisco Meraki MX security appliances with your own Dashboard API key. You bring your own Meraki Appliances 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 Appliances 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 Appliances 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 Appliances receives. The request we make on your behalf, including the key and the arguments, under Meraki Appliances's own terms and privacy policy. Meraki Appliances 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 Appliances 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 Appliances 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 Appliances (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 Appliances at any time to end all access.

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

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

Meraki Appliances (BYOK) — Terms of Service

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

1. The Service. Meraki Appliances (BYOK) provides: Read the uplink status, VPN health, uplink usage and L3 interfaces of your Cisco Meraki MX security appliances 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 Appliances credentials and only access data you are allowed to access. Meraki Appliances's terms apply to your use of Meraki Appliances; 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 Appliances. Meraki Appliances 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 Appliances returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Appliances. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Appliances 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 Appliances'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 Appliances 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 Appliances 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 Appliances 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-appliance

Meraki Appliances (BYOK) support

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

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