Hostinger (BYOK)
Read your Hostinger domains, DNS records, VPS servers, web hosting sites and subscriptions with your own API token
Discover
OpenAPIRead your data8 tools
Meraki Fleet Health (BYOK)
Read device model counts, availability, provisioning, power modules, WAN latency, license and end-of-life summaries of your Cisco Meraki fleet with your own key
Unify Dynamics LLC
Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderMeraki Fleet Healthunofficial, not affiliated
Works withMCP · RESTany agent
Try asking
Real questions, and the tools your agent calls to answer them.
How many of each Meraki hardware model do we run?
Tools called
get_device_counts_by_modelWhich Meraki devices are currently offline?
Tools called
list_device_availabilitiesWhich Meraki devices went offline in the last day?
Tools called
list_availability_changesWhich Meraki devices are not fully provisioned?
Tools called
list_provisioning_statusesAre any power supplies failing on my Meraki switches?
Tools called
list_power_module_statusesWhat is the WAN latency and packet loss on my Meraki MX appliances?
Tools called
get_wan_loss_and_latencyAbout
Meraki Fleet Health (BYOK) lets an AI assistant read your own Meraki Fleet Health data through the Meraki Fleet Health API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 8 tools (get_device_counts_by_model, list_device_availabilities, list_availability_changes, list_provisioning_statuses, list_power_module_statuses, get_wan_loss_and_latency, get_license_overview, get_end_of_life_overview). 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 Fleet Health. Meraki Fleet Health and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Meraki Fleet Health 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.
Privacy
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
Data not collectedNo account, no profile, no stored prompts or results.
What it can do
8 tools, grouped by job. Every one is read-only or compute-only.
- Get device counts by modelCount the devices of an organization per hardware model, optionally for one network or device family.
- List device availabilitiesList the availability (online, alerting, offline or dormant) of devices in an organization with name, MAC, serial, network, device family and tags.
- List availability changesList availability change events of devices (went offline, came back) in a time window with device, network and the old and new status.
- List provisioning statusesList the provisioning status (complete, incomplete or unprovisioned) of devices in an organization.
- List power module statusesList the latest power module status of rackmount MX and MS devices: device name, serial, network and the module slots with their state.
- Get wan loss and latencyGet the uplink packet loss and latency time series of every MX appliance for a window of at most 5 minutes ending at least 2 minutes ago, per…
- Get license overviewGet the license state of an organization: overall status, expiration date, license count, counts by state (active, expired, expiring, unused) and…
- Get end of life overviewSummarize how many devices of the inventory are end-of-sale, end-of-support or near end-of-support.
Information
PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpoint
https://byok-meraki-fleet-health.connectorbay.com/mcpREST APIopenapi.json
CountryWorldwide
FunctionOther
LayerDeep connectors
Connect it to your agent
Three ways in, the same 8 tools.
MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)
https://byok-meraki-fleet-health.connectorbay.com/mcpREST
POST https://byok-meraki-fleet-health.connectorbay.com/v1/tools/<tool>OpenAI function calling
https://connectorbay.com/openai/byok-meraki-fleet-health.jsonOpenAI-compatible chat
https://connectorbay.com/v1/chat/completions · how it works- Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
- Key: send your Meraki Dashboard API key (Organization > API & Webhooks) in the
X-Upstream-Keyheader (get one at dashboard.meraki.com). - Ask a question; the agent picks the right tool and answers from the live data.
Meraki Fleet Health connector: questions and answers
What is the Meraki Fleet Health connector?
Meraki Fleet Health (BYOK) lets an AI assistant read your own Meraki Fleet Health data through the Meraki Fleet Health API with a key you supply… It is a hosted MCP server with 8 tools such as Get device counts by model, List device availabilities, List availability changes, List provisioning statuses, List power module statuses, Get wan loss and latency, published by Unify Dynamics LLC. It is independent and not affiliated with Meraki Fleet Health.
How do I connect Meraki Fleet Health to Claude, ChatGPT or Cursor?
Add the MCP endpoint https://byok-meraki-fleet-health.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-meraki-fleet-health.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-meraki-fleet-health.json.
Do I need a Meraki Fleet Health account or API key?
Yes: this is a bring-your-own-key connector. Create a Meraki Dashboard API key (Organization > API & Webhooks) at https://dashboard.meraki.com/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Is Meraki Fleet Health read-only?
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Is the Meraki Fleet Health connector free?
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
More like this
More in OtherHubSpot CMS Site Settings (BYOK)
Read your HubSpot connected domains, URL redirects, content audit log and public site search with your own private app access token
HubSpot CRM Limits (BYOK)
Read how much of your HubSpot CRM limits you have used: record counts, custom properties, pipelines, custom objects and association labels, with your own private app token
HubSpot Files (BYOK)
Search and read metadata of files and folders in your HubSpot file manager (names, sizes, types, paths) with your own private app access token
HubSpot Marketing Emails (BYOK)
Read your HubSpot marketing emails, their send statistics, revisions and A/B test variants with your own private app access token
HubSpot Settings (BYOK)
Read your HubSpot users (without email addresses), teams, roles, record owners and business units with your own private app access token
Documentation
Back to topMeraki Fleet Health (BYOK) — connector documentation
- MCP endpoint:
https://byok-meraki-fleet-health.connectorbay.com/mcp - REST API:
POST https://byok-meraki-fleet-health.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-meraki-fleet-health.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Meraki Fleet Health Meraki Dashboard API key (Organization > API & Webhooks), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-meraki-fleet-health.connectorbay.com/health· Tool schemas:https://byok-meraki-fleet-health.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-meraki-fleet-health · agent@connectorbay.com
What Meraki Fleet Health (BYOK) is for
Meraki Fleet Health (BYOK) lets an AI assistant read your own Meraki Fleet Health data through the Meraki Fleet Health API with a key you supply (Meraki Dashboard API key (Organization > API & Webhooks)). Read-only: 8 tools (get_device_counts_by_model, list_device_availabilities, list_availability_changes, list_provisioning_statuses, list_power_module_statuses, get_wan_loss_and_latency, get_license_overview, get_end_of_life_overview). 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 Fleet Health. Meraki Fleet Health 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:
- "How many of each Meraki hardware model do we run?"
- "Which Meraki devices are currently offline?"
- "Which Meraki devices went offline in the last day?"
- "Which Meraki devices are not fully provisioned?"
- "Are any power supplies failing on my Meraki switches?"
- "What is the WAN latency and packet loss on my Meraki MX appliances?"
What it does
get_device_counts_by_model: Count the devices of an organization per hardware model, optionally for one network or device family.list_device_availabilities: List the availability (online, alerting, offline or dormant) of devices in an organization with name, MAC, serial, network, device family and tags.list_availability_changes: List availability change events of devices (went offline, came back) in a time window with device, network and the old and new status.list_provisioning_statuses: List the provisioning status (complete, incomplete or unprovisioned) of devices in an organization.list_power_module_statuses: List the latest power module status of rackmount MX and MS devices: device name, serial, network and the module slots with their state.get_wan_loss_and_latency: Get the uplink packet loss and latency time series of every MX appliance for a window of at most 5 minutes ending at least 2 minutes ago, per uplink and probe IP.get_license_overview: Get the license state of an organization: overall status, expiration date, license count, counts by state (active, expired, expiring, unused) and by license type. License keys are not returned.get_end_of_life_overview: Summarize how many devices of the inventory are end-of-sale, end-of-support or near end-of-support.
BYOK key
You bring your own Meraki Fleet Health 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 Fleet Health 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 Fleet Health. Meraki Fleet Health 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 Fleet Health account.
Built for: Worldwide. Languages: English.
Privacy policy
Back to topMeraki Fleet Health (BYOK) — Privacy Policy
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Meraki Fleet Health (BYOK) is. Meraki Fleet Health (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meraki Fleet Health data: Read device model counts, availability, provisioning, power modules, WAN latency, license and end-of-life summaries of your Cisco Meraki fleet with your own key. You bring your own Meraki Fleet Health 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 Fleet Health 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 Fleet Health 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 Fleet Health receives. The request we make on your behalf, including the key and the arguments, under Meraki Fleet Health's own terms and privacy policy. Meraki Fleet Health 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 Fleet Health 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 Fleet Health 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 Fleet Health (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 Fleet Health at any time to end all access.
Children. Meraki Fleet Health (BYOK) is a general-audience service operated by the adult using the assistant, under Meraki Fleet Health's own age rules.
Changes. We will post changes here with a new effective date.
Terms of service
Back to topMeraki Fleet Health (BYOK) — Terms of Service
Effective 24 October 2026. These terms govern use of the Meraki Fleet Health (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
- The Service. Meraki Fleet Health (BYOK) provides: Read device model counts, availability, provisioning, power modules, WAN latency, license and end-of-life summaries of your Cisco Meraki fleet with your own key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
- Your own key, your own account. You must use your own Meraki Fleet Health credentials and only access data you are allowed to access. Meraki Fleet Health's terms apply to your use of Meraki Fleet Health; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
- Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Meraki Fleet Health. Meraki Fleet Health and its logos are trademarks of their owners and are used only to say which service the connector works with.
- No advice, no guarantees. Output is the data Meraki Fleet Health returns, lightly trimmed; it may be incomplete, delayed or changed by Meraki Fleet Health. Check important facts at the source.
- Read-only. The Service does not create, change, send or delete anything in your Meraki Fleet Health account.
- 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 Fleet Health's controls, or to attack any system.
- Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Meraki Fleet Health may change or end its API at any time.
- Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
- Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Meraki Fleet Health key.
- 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 Fleet Health takes on your account. Our total liability is limited to US $100.
- Governing law. California law; venue in San Mateo County, California.
- Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-meraki-fleet-health
Support
Back to topMeraki Fleet Health (BYOK) support
Email agent@connectorbay.com. We answer within two business days.
- MCP endpoint:
https://byok-meraki-fleet-health.connectorbay.com/mcp - REST API:
https://byok-meraki-fleet-health.connectorbay.com/openapi.json - Live status: https://byok-meraki-fleet-health.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 Fleet Health (BYOK) never asks for them.