Meraki Switches (BYOK)

Meraki Switches (BYOK) — connector documentation

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

What Meraki Switches (BYOK) is for

Meraki Switches (BYOK) lets an AI assistant read your own Meraki Switches data through the Meraki Switches API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 7 tools (list_switch_ports, list_switch_port_statuses, get_switch_ports_overview, list_switch_port_client_counts, list_switch_port_neighbors, get_switch_port_usage_history, get_switch_poe_history). 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 Switches. Meraki Switches 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 is the port configuration of my Meraki switches?"
• "Which ports on my Meraki switches are down or have errors?"
• "How many of my Meraki switch ports are active?"
• "How many clients are plugged into each Meraki switch port?"
• "What devices are connected to my Meraki switch ports according to LLDP?"
• "How much traffic did my Meraki switch ports carry yesterday?"

What it does

• list_switch_ports: List the switch ports of an organization grouped by switch: switch name, serial, MAC, network, model and the ports with their configuration.
• list_switch_port_statuses: List the live status of each switch port per switch: link state, speed, duplex, PoE power, errors and warnings.
• get_switch_ports_overview: Count the active and inactive switch ports of an organization over a period, grouped by link speed.
• list_switch_port_client_counts: List the number of clients on each switch port that had at least one online client in a period (counts only, no client details).
• list_switch_port_neighbors: List the most recently seen LLDP and CDP neighbor information per switch port: which devices are connected to which port.
• get_switch_port_usage_history: List historical traffic and usage of switch ports per switch over a window, bucketed by an interval.
• get_switch_poe_history: Get the total PoE power draw of all switch ports in an organization over a window as a time series in watts.

BYOK key

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

Built for: Worldwide. Languages: English.

Meraki Switches (BYOK) — Privacy Policy

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

What Meraki Switches (BYOK) is. Meraki Switches (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Switches data: Read the port configuration, port status, port usage, client counts, LLDP/CDP neighbors and PoE draw of your Cisco Meraki switches with your own Dashboard API key. You bring your own Meraki Switches 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 Switches 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 Switches 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 Switches receives. The request we make on your behalf, including the key and the arguments, under Meraki Switches's own terms and privacy policy. Meraki Switches 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 Switches 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 Switches 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 Switches (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 Switches at any time to end all access.

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

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

Meraki Switches (BYOK) — Terms of Service

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

1. The Service. Meraki Switches (BYOK) provides: Read the port configuration, port status, port usage, client counts, LLDP/CDP neighbors and PoE draw of your Cisco Meraki switches 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 Switches credentials and only access data you are allowed to access. Meraki Switches's terms apply to your use of Meraki Switches; 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 Switches. Meraki Switches 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 Switches returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Switches. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Switches 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 Switches'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 Switches 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 Switches 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 Switches 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-switch

Meraki Switches (BYOK) support

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

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