Meraki Usage Summary (BYOK)

Meraki Usage Summary (BYOK) — connector documentation

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

What Meraki Usage Summary (BYOK) is for

Meraki Usage Summary (BYOK) lets an AI assistant read your own Meraki Usage Summary data through the Meraki Usage Summary API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 8 tools (get_top_appliances_by_utilization, get_top_devices_by_usage, get_top_device_models_by_usage, get_top_ssids_by_usage, get_top_applications_by_usage, get_top_application_categories_by_usage, get_top_switches_by_energy_usage, list_networks_by_status). 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 Usage Summary. Meraki Usage Summary 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 appliances are the most heavily utilized?"
• "Which Meraki devices carried the most traffic last week?"
• "Which Meraki hardware models carry the most traffic?"
• "Which SSIDs use the most data in my Meraki organization?"
• "Which applications use the most bandwidth in my Meraki organization?"
• "Which application categories use the most bandwidth in my Meraki organization?"

What it does

• get_top_appliances_by_utilization: List the top appliances of an organization by utilization over a window, with network, name, MAC, serial, model and average utilization.
• get_top_devices_by_usage: List the top devices of an organization by data usage over a window, with name, model, serial, MAC, device family, network, usage and client counts.
• get_top_device_models_by_usage: List the top device hardware models of an organization by data usage over a window, with model, device count and total and average usage.
• get_top_ssids_by_usage: List the top SSIDs of an organization by data usage over a window, with name, usage and client counts.
• get_top_applications_by_usage: List the top applications by data usage across the organization over a window, with total, downstream and upstream usage and share.
• get_top_application_categories_by_usage: List the top application categories by data usage across the organization over a window, with total, downstream and upstream usage and share.
• get_top_switches_by_energy_usage: List the top switches of an organization by energy usage over a window, with network, name, MAC, model and total usage.
• list_networks_by_status: List the networks of an organization with overall status (online, alerting, offline or dormant), device counts by product type, client counts and usage.

BYOK key

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

Built for: Worldwide. Languages: English.

Meraki Usage Summary (BYOK) — Privacy Policy

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

What Meraki Usage Summary (BYOK) is. Meraki Usage Summary (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Usage Summary data: Read top-N usage summaries of your Cisco Meraki organization: busiest appliances, devices, device models, SSIDs, applications, switches by energy and networks by status. You bring your own Meraki Usage Summary 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 Usage Summary 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 Usage Summary 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 Usage Summary receives. The request we make on your behalf, including the key and the arguments, under Meraki Usage Summary's own terms and privacy policy. Meraki Usage Summary 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 Usage Summary 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 Usage Summary 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 Usage Summary (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 Usage Summary at any time to end all access.

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

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

Meraki Usage Summary (BYOK) — Terms of Service

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

1. The Service. Meraki Usage Summary (BYOK) provides: Read top-N usage summaries of your Cisco Meraki organization: busiest appliances, devices, device models, SSIDs, applications, switches by energy and networks by status. 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 Usage Summary credentials and only access data you are allowed to access. Meraki Usage Summary's terms apply to your use of Meraki Usage Summary; 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 Usage Summary. Meraki Usage Summary 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 Usage Summary returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Usage Summary. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Usage Summary 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 Usage Summary'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 Usage Summary 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 Usage Summary 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 Usage Summary 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-usage-summary

Meraki Usage Summary (BYOK) support

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

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