Meraki Sensors (BYOK)

Meraki Sensors (BYOK) — connector documentation

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

What Meraki Sensors (BYOK) is for

Meraki Sensors (BYOK) lets an AI assistant read your own Meraki Sensors data through the Meraki Sensors API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 7 tools (get_latest_readings, get_reading_history, get_current_alert_overview, get_alert_history_overview, list_alert_profiles, list_gateway_connections, list_sensor_relationships). 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 Sensors. Meraki Sensors 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 current temperature and humidity on my Meraki sensors?"
• "Show the temperature history of Meraki sensor Q3CA-AAAA-0001 for the last day"
• "How many Meraki sensors in network L_646829496481105433 are alerting now?"
• "How many Meraki sensor alerts fired per day last week in network L_646829496481105433?"
• "Which alert rules do my Meraki sensors in network L_646829496481105433 have?"
• "Which Meraki sensors have a weak link to their gateway?"

What it does

• get_latest_readings: Get the latest reading of each metric (temperature, humidity, CO2, noise, door, water and more) from each sensor in an organization, optionally for one network, sensor or metric.
• get_reading_history: Get historical sensor readings of an organization in a time window of up to 7 days, oldest first, optionally for one network, sensor or metric.
• get_current_alert_overview: Count the sensors that are alerting right now in a network, per metric.
• get_alert_history_overview: Count sensor alert occurrences of a network per metric over a period, bucketed by an interval (15 minutes, 1 hour, 1 day, 1 week or 1 month).
• list_alert_profiles: List the sensor alert profiles of a network: name, conditions (metric, threshold, direction, duration), schedule and the sensor serials they cover. Recipient contact details are not returned.
• list_gateway_connections: List the latest connection of each sensor to its gateway: last report time, signal strength (RSSI), and the sensor and gateway serials and names.
• list_sensor_relationships: List the sensor roles of the sensor and camera devices in a network, such as which sensors relate to which camera for live view.

BYOK key

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

Built for: Worldwide. Languages: English.

Meraki Sensors (BYOK) — Privacy Policy

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

What Meraki Sensors (BYOK) is. Meraki Sensors (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Sensors data: Read the latest and historical readings, alert counts and gateway links of your Cisco Meraki MT environmental sensors with your own Dashboard API key. You bring your own Meraki Sensors 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 Sensors 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 Sensors 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 Sensors receives. The request we make on your behalf, including the key and the arguments, under Meraki Sensors's own terms and privacy policy. Meraki Sensors 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 Sensors 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 Sensors 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 Sensors (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 Sensors at any time to end all access.

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

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

Meraki Sensors (BYOK) — Terms of Service

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

1. The Service. Meraki Sensors (BYOK) provides: Read the latest and historical readings, alert counts and gateway links of your Cisco Meraki MT environmental sensors 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 Sensors credentials and only access data you are allowed to access. Meraki Sensors's terms apply to your use of Meraki Sensors; 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 Sensors. Meraki Sensors 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 Sensors returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Sensors. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meraki Sensors 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 Sensors'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 Sensors 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 Sensors 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 Sensors 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-sensor

Meraki Sensors (BYOK) support

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

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