Meraki Health Alerts (BYOK)

Meraki Health Alerts (BYOK) — connector documentation

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

What Meraki Health Alerts (BYOK) is for

Meraki Health Alerts (BYOK) lets an AI assistant read your own Meraki Health Alerts data through the Meraki Health Alerts API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 8 tools (list_health_alerts, get_health_alert, get_alert_overview, get_alert_overview_by_type, get_alert_overview_by_network, get_alert_overview_history, list_alert_types, list_alert_categories). 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 Health Alerts. Meraki Health Alerts 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 critical Meraki health alerts are active right now?"
• "Show Meraki health alert 123"
• "How many Meraki health alerts are active by severity?"
• "Which Meraki alert types fire most often?"
• "Which of my Meraki networks have the most health alerts?"
• "How many Meraki health alerts were there per day in the last week?"

What it does

• list_health_alerts: List the health alerts of an organization with network, category, type, title, severity, start, resolution and dismissal time. Filter by network, severity, category, type or whether still active.
• get_health_alert: Get one health alert by id with network, type, title, description, severity, timing and the affected devices, applications and peers.
• get_alert_overview: Count the health alerts of an organization in total and by severity, with optional filters.
• get_alert_overview_by_type: Summarize health alerts grouped by alert type and severity: count, number of networks, last alert and last resolution time.
• get_alert_overview_by_network: Summarize health alerts grouped by network: alert count, last alert time and counts per severity.
• get_alert_overview_history: Get historical health alert totals per time segment, with a breakdown by alert type. segment_duration and ts_start are required.
• list_alert_types: List all health alert types known to the organization with title, category, severities and applicable device types.
• list_alert_categories: List the health alert category types with their titles.

BYOK key

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

Built for: Worldwide. Languages: English.

Meraki Health Alerts (BYOK) — Privacy Policy

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

What Meraki Health Alerts (BYOK) is. Meraki Health Alerts (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Health Alerts data: Read the health alerts, alert counts by type or network, alert history and alert taxonomy of your Cisco Meraki organization with your own Dashboard API key. You bring your own Meraki Health Alerts 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 Health Alerts 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 Health Alerts 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 Health Alerts receives. The request we make on your behalf, including the key and the arguments, under Meraki Health Alerts's own terms and privacy policy. Meraki Health Alerts 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 Health Alerts 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 Health Alerts 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 Health Alerts (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 Health Alerts at any time to end all access.

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

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

Meraki Health Alerts (BYOK) — Terms of Service

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

1. The Service. Meraki Health Alerts (BYOK) provides: Read the health alerts, alert counts by type or network, alert history and alert taxonomy of your Cisco Meraki organization 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 Health Alerts credentials and only access data you are allowed to access. Meraki Health Alerts's terms apply to your use of Meraki Health Alerts; 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 Health Alerts. Meraki Health Alerts 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 Health Alerts returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Health Alerts. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Health Alerts 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 Health Alerts'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 Health Alerts 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 Health Alerts 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 Health Alerts 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-assurance

Meraki Health Alerts (BYOK) support

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

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