Skip to content
actionlake
Start free

Connectors · MSP & PSA

Cisco Meraki Dashboard API MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Cisco Meraki Dashboard API and the rest of your systems. It gives your agent 1,039 Cisco Meraki Dashboard API actions (557 reads, 371 writes and 111 that wait for a confirmation) and holds the Cisco Meraki Dashboard API credential itself, so the agent never does. It paces Cisco Meraki Dashboard API's limits and records every call.

Connect Cisco Meraki Dashboard API freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "cisco_meraki_dashboard.organizations.get_organizations",  intent: "check which Cisco Meraki Dashboard API account is connected"}# List the organizations that the user has privileges on · read · 1 upstream call
  • 1,039actionsin one signed file
  • 557readlook, never change
  • 371writecreate and update
  • 111wait for a yesdestructive, confirmed first

Set up

Connect Cisco Meraki Dashboard API in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Cisco Meraki Dashboard API.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyMeraki Dashboard API key
    • hostWhere your Cisco Meraki Dashboard API lives: your host
    account { op: "connections.requirements", service: "cisco_meraki_dashboard" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "cisco_meraki_dashboard.organizations.get_organizations" }# list the organizations that the user has privileges on · read · 1 upstream callcheck { action: "cisco_meraki_dashboard.devices.update_device", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Cisco Meraki Dashboard API at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Setup fields
host
Limits we pace to
10 calls a second, per connection
API covered
Meraki Dashboard API v1.75.1 (OpenAPI 3), at your Cisco Meraki Dashboard API instance's API base URL, which you enter when connecting (path /api/v1)
Built from
Cisco Meraki Dashboard API's documentation, read 22 October 2026OpenAPI spec (GitHub)developer.cisco.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
556 of 557 reads, for up to 5 minutes; a write clears what it affects
Shared entities
6, so ask can line Cisco Meraki Dashboard API up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Cisco Meraki Dashboard API.

1,039 actions in 16 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 557readlook, never change
  • 371writecreate and update
  • 111destructivewait for a confirmation

  1. Organizations

    251

    133 read · 80 write · 38 destructive

    List the dashboard administrators in this organization · List the devices in an organization that have been assigned to a network · List the organizations that the user has privileges on · List the licenses for an organization

  2. Appliance

    181

    86 read · 78 write · 17 destructive

    Add one Cisco Umbrella DNS security policy to an MX network by policy ID · Assign VLANs to a policy · Assign the local DNS profile to networks in the organization · Upload an HTTPS Inspection certificate to MX devices in the same organization

  3. Wireless

    157

    93 read · 55 write · 9 destructive

    Assign AP port profile to list of APs · Enqueue a job to start enrolling door locks on zigbee configured wireless devices · Creates a new rule · Create an AP port profile

  4. Networks

    115

    57 read · 45 write · 13 destructive

    Return a network · Schedule auto locate jobs for one or more floor plans in a network · Update floorplan assignments for a batch of devices · Bind a network to a template

  5. Switch

    102

    49 read · 40 write · 13 destructive

    Add a switch to a stack · Clone port-level and some switch-level configuration settings from a source switch to one or more target switches · Create a layer 3 interface for a switch · Create a layer 3 static route for a switch

  6. SM

    49

    28 read · 11 write · 10 destructive

    List the devices enrolled in an SM network with various specified fields and filters · Force check-in a set of devices · Bypass activation lock attempt · Add a target group

  7. Camera

    46

    28 read · 14 write · 4 destructive

    Creates new quality retention profile for this network · Creates a new camera wireless profile for this network · Create custom analytics artifact · Creates new role for this organization

  8. Devices

    41

    20 read · 20 write · 1 destructive

    Return a single device · Update the attributes of a device · Blink the LEDs on a device · Update the cellular band masks for a device

8 more areas · 97 actions
  • Cellular gateway 24
  • Sensor 19
  • Campus gateway 18
  • Wireless controller 15
  • Licensing 8
  • Insight 7
  • Administered 4
  • Spaces 2

Top actions

The Cisco Meraki Dashboard API API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 11 of Cisco Meraki Dashboard API's 11 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
cisco_meraki_dashboard.organizations.get_organization_adminsList the dashboard administrators in this organizationList the dashboard administrators in this organizationreadidentity.user.list474 connectors
cisco_meraki_dashboard.organizations.get_organization_devicesList the devices in an organization that have been assigned to a networkList the devices in an organization that have been assigned to a network.readasset.asset.list42 connectors
cisco_meraki_dashboard.organizations.get_organizationsList the organizations that the user has privileges onList the organizations that the user has privileges onreadcrm.company.list162 connectors
cisco_meraki_dashboard.sm.get_network_sm_devicesList the devices enrolled in an SM network with various specified fields and filtersList the devices enrolled in an SM network with various specified fields and filtersreaddevice.endpoint.list65 connectors
cisco_meraki_dashboard.devices.get_deviceReturn a single deviceReturn a single devicereadasset.asset.get40 connectors
cisco_meraki_dashboard.organizations.get_organization_licensesList the licenses for an organizationList the licenses for an organizationreadidentity.license.list10 connectors
cisco_meraki_dashboard.devices.update_deviceUpdate the attributes of a deviceUpdate the attributes of a devicewriteasset.asset.update34 connectors
cisco_meraki_dashboard.organizations.get_organization_networksList the networks that the user has privileges on in an organizationList the networks that the user has privileges on in an organizationreadsecurity.network.list15 connectors
cisco_meraki_dashboard.organizations.get_organizationReturn an organizationReturn an organizationreadcrm.company.get162 connectors
cisco_meraki_dashboard.networks.bind_networkBind a network to a templateBind a network to a template.writethis connector
cisco_meraki_dashboard.networks.split_networkSplit a combined network into individual networks for each type of deviceSplit a combined network into individual networks for each type of devicewritethis connector
cisco_meraki_dashboard.devices.reboot_deviceReboot a deviceReboot a devicedestructivethis connector

Try it

Prompts to paste into Claude.

Each one names the Cisco Meraki Dashboard API actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Cisco Meraki Dashboard API devices have not checked in for a week?

    callscisco_meraki_dashboard.sm.get_network_sm_devices

  2. Writewrite

    Update the attributes of a device in Cisco Meraki Dashboard API. Show me exactly what you will send before you save it.

    callscisco_meraki_dashboard.devices.update_device

  3. Across systemsread

    Which Cisco Meraki Dashboard API companies have invoices in NetSuite, and how many each?

    callscisco_meraki_dashboard.organizations.get_organizationsnetsuite.views.invoices

Across your systems

Cisco Meraki Dashboard API, joined to the rest of your business.

One ask fetches from Cisco Meraki Dashboard API and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

  • Which Cisco Meraki Dashboard API companies have invoices in NetSuite, and how many each?

    cisco_meraki_dashboard.organizations.get_organizations + netsuite.views.invoices, on crm.company · NetSuite

  • Which Cisco Meraki Dashboard API companies have tickets in HubSpot CRM, and how many each?

    cisco_meraki_dashboard.organizations.get_organizations + hubspot_crm.tickets.list, on crm.company · HubSpot CRM

Also mapped by other connectorsidentity.user 517crm.company 227device.endpoint 69asset.asset 40security.network 12identity.license 4
ask
ask {  intent: "which Cisco Meraki Dashboard API companies have invoices in NetSuite, and how many each",  steps: [    { action: "cisco_meraki_dashboard.organizations.get_organizations", as: "co", input: {}, limit: 100, max_pages: 5 },    { action: "netsuite.views.invoices", as: "inv", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "co",        right: "inv",        on: "crm.company",        group_by: "co.name",        select: ["co.name", "count(inv.id) as invoices"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Cisco Meraki Dashboard API

Destructive actions wait for a yes.

111 Cisco Meraki Dashboard API actions are destructive. The first 10:

  • Reboot a devicecisco_meraki_dashboard.devices.reboot_device
  • Delete a networkcisco_meraki_dashboard.networks.delete_network
  • Unbind a network from a templatecisco_meraki_dashboard.networks.unbind_network
  • Lock a set of devicescisco_meraki_dashboard.sm.lock_network_sm_devices
  • Wipe a devicecisco_meraki_dashboard.sm.wipe_network_sm_devices
  • Reboot a set of endpointscisco_meraki_dashboard.sm.reboot_network_sm_devices
  • Unenroll a devicecisco_meraki_dashboard.sm.unenroll_network_sm_device
  • Shutdown a set of endpointscisco_meraki_dashboard.sm.shutdown_network_sm_devices
  • Remove a single devicecisco_meraki_dashboard.networks.remove_network_devices
  • Cycle a set of switch ports on non-Catalyst MS devicescisco_meraki_dashboard.switch.cycle_device_switch_ports

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

docisco_meraki_dashboard.networks.delete_networkconfirm_policy: human

Delete a network?

intent: the user asked me to delete a network

run suspended · waiting for a named person · key cisco-meraki-dashboard-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "cisco-meraki-dashboard-agent",  allowed_actions: ["cisco_meraki_dashboard.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "cisco_meraki_dashboard.devices.reboot_device", approver: "[email protected]" },    { match: "cisco_meraki_dashboard.networks.delete_network", approver: "[email protected]" },    { match: "cisco_meraki_dashboard.networks.unbind_network", approver: "[email protected]" }  ]}
Illustrative. Scoped to Cisco Meraki Dashboard API only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Cisco Meraki Dashboard API costs on actionlake.

Every Cisco Meraki Dashboard API action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Cisco Meraki Dashboard API refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 1,039 Cisco Meraki Dashboard API actions
  • 1,039actions pageeach page of a long list is one call
  • 556reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Cisco Meraki Dashboard API action.

1,039 actions by area: the id your agent calls, what it does, and its effect.

Organizations251
  • cisco_meraki_dashboard.organizations.get_organization_adminsList the dashboard administrators in this organizationread
  • cisco_meraki_dashboard.organizations.get_organization_devicesList the devices in an organization that have been assigned to a networkread
  • cisco_meraki_dashboard.organizations.get_organization_licensesList the licenses for an organizationread
  • cisco_meraki_dashboard.organizations.get_organizationsList the organizations that the user has privileges onread
  • cisco_meraki_dashboard.organizations.assign_organization_licenses_seatsAssign SM seats to a networkwrite
  • cisco_meraki_dashboard.organizations.assign_organization_policies_global_group_policies_adaptive_policy_groupsAssign adaptive policy groups to a policywrite
  • and 245 more in this area
Appliance181
  • cisco_meraki_dashboard.appliance.add_network_appliance_umbrella_policiesAdd one Cisco Umbrella DNS security policy to an MX network by policy IDwrite
  • cisco_meraki_dashboard.appliance.assign_organization_policies_global_group_policies_appliance_vlansAssign VLANs to a policywrite
  • cisco_meraki_dashboard.appliance.bulk_organization_appliance_dns_local_profiles_assignments_createAssign the local DNS profile to networks in the organizationwrite
  • cisco_meraki_dashboard.appliance.certificates_organization_appliance_security_httpsiUpload an HTTPS Inspection certificate to MX devices in the same organizationwrite
  • cisco_meraki_dashboard.appliance.connect_network_appliance_umbrella_accountConnect a Cisco Umbrella account to this networkwrite
  • cisco_meraki_dashboard.appliance.create_device_appliance_interfaces_ports_updateUpdate configurations for an appliance's specified portwrite
  • and 175 more in this area
Wireless157
  • cisco_meraki_dashboard.wireless.assign_network_wireless_ethernet_ports_profilesAssign AP port profile to list of APswrite
  • cisco_meraki_dashboard.wireless.create_device_wireless_zigbee_enrollmentEnqueue a job to start enrolling door locks on zigbee configured wireless deviceswrite
  • cisco_meraki_dashboard.wireless.create_network_wireless_air_marshal_ruleCreates a new rulewrite
  • cisco_meraki_dashboard.wireless.create_network_wireless_ethernet_ports_profileCreate an AP port profilewrite
  • cisco_meraki_dashboard.wireless.create_network_wireless_rf_profileCreates new RF profile for this networkwrite
  • cisco_meraki_dashboard.wireless.create_network_wireless_ssid_identity_pskCreate an Identity PSKwrite
  • and 151 more in this area
Networks115
  • cisco_meraki_dashboard.networks.batch_network_floor_plans_auto_locate_jobsSchedule auto locate jobs for one or more floor plans in a networkwrite
  • cisco_meraki_dashboard.networks.batch_network_floor_plans_devices_updateUpdate floorplan assignments for a batch of deviceswrite
  • cisco_meraki_dashboard.networks.bind_networkBind a network to a templatewrite
  • cisco_meraki_dashboard.networks.get_networkReturn a networkread
  • cisco_meraki_dashboard.networks.cancel_network_floor_plans_auto_locate_jobCancel a scheduled or running auto locate jobdestructive
  • cisco_meraki_dashboard.networks.claim_network_devicesClaim devices into a network. (Note: for recently claimed devices, it may take a few minutes for API requests against that device to succeed)write
  • and 109 more in this area
Switch102
  • cisco_meraki_dashboard.switch.add_network_switch_stackAdd a switch to a stackwrite
  • cisco_meraki_dashboard.switch.clone_organization_switch_devicesClone port-level and some switch-level configuration settings from a source switch to one or more target switcheswrite
  • cisco_meraki_dashboard.switch.create_device_switch_routing_interfaceCreate a layer 3 interface for a switchwrite
  • cisco_meraki_dashboard.switch.create_device_switch_routing_static_routeCreate a layer 3 static route for a switchwrite
  • cisco_meraki_dashboard.switch.create_network_switch_access_policyCreate an access policy for a switch networkwrite
  • cisco_meraki_dashboard.switch.create_network_switch_dhcp_server_policy_arp_inspection_trusted_serverAdd a server to be trusted by Dynamic ARP Inspection on this networkwrite
  • and 96 more in this area
SM49
  • cisco_meraki_dashboard.sm.checkin_network_sm_devicesForce check-in a set of deviceswrite
  • cisco_meraki_dashboard.sm.create_network_sm_bypass_activation_lock_attemptBypass activation lock attemptwrite
  • cisco_meraki_dashboard.sm.create_network_sm_target_groupAdd a target groupwrite
  • cisco_meraki_dashboard.sm.get_network_sm_devicesList the devices enrolled in an SM network with various specified fields and filtersread
  • cisco_meraki_dashboard.sm.create_organization_sm_admins_roleCreate a Limited Access Roledestructive
  • cisco_meraki_dashboard.sm.delete_network_sm_target_groupDelete a target group from a networkdestructive
  • and 43 more in this area
Camera46
  • cisco_meraki_dashboard.camera.create_network_camera_quality_retention_profileCreates new quality retention profile for this networkwrite
  • cisco_meraki_dashboard.camera.create_network_camera_wireless_profileCreates a new camera wireless profile for this networkwrite
  • cisco_meraki_dashboard.camera.create_organization_camera_custom_analytics_artifactCreate custom analytics artifactwrite
  • cisco_meraki_dashboard.camera.create_organization_camera_roleCreates new role for this organizationwrite
  • cisco_meraki_dashboard.camera.clip_device_cameraGenerate a video clip of up to 5 minutes longread
  • cisco_meraki_dashboard.camera.delete_network_camera_quality_retention_profileDelete an existing quality retention profile for this networkdestructive
  • and 40 more in this area
Devices41
  • cisco_meraki_dashboard.devices.blink_device_ledsBlink the LEDs on a devicewrite
  • cisco_meraki_dashboard.devices.create_device_cellular_uplinks_bands_masks_updateUpdate the cellular band masks for a devicewrite
  • cisco_meraki_dashboard.devices.get_deviceReturn a single deviceread
  • cisco_meraki_dashboard.devices.update_deviceUpdate the attributes of a devicewrite
  • cisco_meraki_dashboard.devices.create_device_live_tools_arp_tableEnqueue a job to perform an ARP table request for the devicewrite
  • cisco_meraki_dashboard.devices.create_device_live_tools_cable_testEnqueue a job to perform a cable test for the device on the specified portswrite
  • and 35 more in this area
Cellular gateway24
  • cisco_meraki_dashboard.cellular_gateway.create_organization_cellular_gateway_esims_service_providers_accountAdd a service provider accountwrite
  • cisco_meraki_dashboard.cellular_gateway.create_organization_cellular_gateway_esims_swapSwap which profile an eSIM useswrite
  • cisco_meraki_dashboard.cellular_gateway.get_device_cellular_gateway_lanShow the LAN Settings of an MGread
  • cisco_meraki_dashboard.cellular_gateway.get_organization_cellular_gateway_uplink_statusesList the uplink status of every Meraki MG cellular gateway in the organizationread
  • cisco_meraki_dashboard.cellular_gateway.delete_organization_cellular_gateway_esims_service_providers_accountRemove a service provider account's integration with the Dashboarddestructive
  • cisco_meraki_dashboard.cellular_gateway.get_device_cellular_gateway_port_forwarding_rulesReturns the port forwarding rules for a single MGread
  • and 18 more in this area
Sensor19
  • cisco_meraki_dashboard.sensor.create_device_sensor_commandSends a command to a sensorwrite
  • cisco_meraki_dashboard.sensor.create_network_sensor_alerts_profileCreates a sensor alert profile for a networkwrite
  • cisco_meraki_dashboard.sensor.get_device_sensor_commandsReturns a historical log of all commandsread
  • cisco_meraki_dashboard.sensor.get_organization_sensor_gateways_connections_latestReturns latest sensor-gateway connectivity dataread
  • cisco_meraki_dashboard.sensor.delete_network_sensor_alerts_profileDeletes a sensor alert profile from a networkdestructive
  • cisco_meraki_dashboard.sensor.get_device_sensor_commandReturns information about the command's execution, including the statusread
  • and 13 more in this area
Campus gateway18
  • cisco_meraki_dashboard.campus_gateway.batch_organization_campus_gateway_clusters_tunneling_updateUpdate MCG cluster-network tunnel settings for multiple networkswrite
  • cisco_meraki_dashboard.campus_gateway.create_network_campus_gateway_clusterCreate a cluster and add campus gateways to itwrite
  • cisco_meraki_dashboard.campus_gateway.get_organization_campus_gateway_clients_usage_by_network_by_clusterReturns client usage details for campus gateway clusters within an organizationread
  • cisco_meraki_dashboard.campus_gateway.get_organization_campus_gateway_clustersGet the details of campus gateway clustersread
  • cisco_meraki_dashboard.campus_gateway.delete_network_campus_gateway_clusterDelete a clusterdestructive
  • cisco_meraki_dashboard.campus_gateway.get_organization_campus_gateway_clusters_failover_targetsList the details of a Failover Targets for a Campus Gateway clusterread
  • and 12 more in this area
Wireless controller15
  • cisco_meraki_dashboard.wireless_controller.get_organization_wireless_controller_availabilities_change_historyList connectivity data of wireless LAN controllers in an organizationread
  • cisco_meraki_dashboard.wireless_controller.get_organization_wireless_controller_clients_overview_history_by_device_by_intervalList wireless client counts of wireless LAN controllers over time in an organizationread
  • cisco_meraki_dashboard.wireless_controller.get_organization_wireless_controller_connectionsList all access points associated with wireless LAN controllers in an organizationread
  • cisco_meraki_dashboard.wireless_controller.get_organization_wireless_controller_devices_interfaces_l2_by_deviceList wireless LAN controller layer 2 interfaces in an organizationread
  • cisco_meraki_dashboard.wireless_controller.get_organization_wireless_controller_devices_interfaces_l2_statuses_change_history_by_deviceList wireless LAN controller layer 2 interfaces history status in an organizationread
  • cisco_meraki_dashboard.wireless_controller.get_organization_wireless_controller_devices_interfaces_l2_usage_history_by_intervalList wireless LAN controller layer 2 interfaces history usage in an organizationread
  • and 9 more in this area
Licensing8
  • cisco_meraki_dashboard.licensing.bind_administered_licensing_subscription_subscriptionBind networks to a subscriptionwrite
  • cisco_meraki_dashboard.licensing.claim_administered_licensing_subscription_subscriptionsClaim a subscription into an organizationwrite
  • cisco_meraki_dashboard.licensing.get_administered_licensing_subscription_subscriptionsList available subscriptionsread
  • cisco_meraki_dashboard.licensing.get_organization_licensing_coterm_licensesList the licenses in a coterm organizationread
  • cisco_meraki_dashboard.licensing.get_administered_licensing_subscription_entitlementsRetrieve the list of purchasable entitlementsread
  • cisco_meraki_dashboard.licensing.get_administered_licensing_subscription_subscriptions_compliance_statusesGet compliance status for requested subscriptionsread
  • and 2 more in this area
Insight7
  • cisco_meraki_dashboard.insight.create_organization_insight_monitored_media_serverAdd a media server to be monitored for this organizationwrite
  • cisco_meraki_dashboard.insight.get_network_insight_application_health_by_timeGet application health by timeread
  • cisco_meraki_dashboard.insight.get_organization_insight_applicationsList all Insight tracked applicationsread
  • cisco_meraki_dashboard.insight.get_organization_insight_monitored_media_serverReturn a monitored media server for this organizationread
  • cisco_meraki_dashboard.insight.delete_organization_insight_monitored_media_serverDelete a monitored media server from this organizationdestructive
  • cisco_meraki_dashboard.insight.get_organization_insight_monitored_media_serversList the monitored media servers for this organizationread
  • and 1 more in this area
Administered4
  • cisco_meraki_dashboard.administered.generate_administered_identities_me_api_keysGenerates an API key for an identitywrite
  • cisco_meraki_dashboard.administered.get_administered_identities_meReturns the identity of the current userread
  • cisco_meraki_dashboard.administered.get_administered_identities_me_api_keysList the non-sensitive metadata associated with the API keys that belong to the userread
  • cisco_meraki_dashboard.administered.revoke_administered_identities_me_api_keysRevokes an identity's API key, using the last four characters of the keydestructive
Spaces2
  • cisco_meraki_dashboard.spaces.get_organization_spaces_integrate_statusGet the status of the Spaces integration in Merakiread
  • cisco_meraki_dashboard.spaces.remove_organization_spaces_integrationRemove the Spaces integration from Merakidestructive

This index shows a sample of each area. All 1,039 actions, with their inputs and prices, are in the catalogue, which a free sandbox key can search.

Questions

The Cisco Meraki Dashboard API MCP server, answered.

Is there a Cisco Meraki Dashboard API MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 1,039 Cisco Meraki Dashboard API actions across organizations, appliance, wireless and networks, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Cisco Meraki Dashboard API.

What do I need to connect Cisco Meraki Dashboard API?

Meraki Dashboard API key. Plus your host. The free call account { op: "connections.requirements", service: "cisco_meraki_dashboard" } lists exactly what to paste.

Can an AI agent delete or change things in Cisco Meraki Dashboard API?

Only if its key allows it, and only with an explicit confirmation. 111 Cisco Meraki Dashboard API actions are destructive, including reboot a device, delete a network and unbind a network from a template. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Cisco Meraki Dashboard API API limit?

actionlake paces every call to the limits in the Cisco Meraki Dashboard API service file: 10 calls a second per connection. Repeated reads are answered from cache (556 Cisco Meraki Dashboard API actions can be), which never reaches Cisco Meraki Dashboard API.

What does a Cisco Meraki Dashboard API action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (1,039 Cisco Meraki Dashboard API actions page). Cache hits, searches, dry runs and calls Cisco Meraki Dashboard API refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Cisco Meraki Dashboard API API does it cover?

The Meraki Dashboard API v1.75.1 (OpenAPI 3) at your Cisco Meraki Dashboard API instance's API base URL, which you enter when connecting (path /api/v1). It is built from Cisco Meraki Dashboard API's documentation as read on 22 October 2026. 1,039 actions in 16 areas, each one in the signed service file (version 1.0.0).

Can I combine Cisco Meraki Dashboard API with my other systems?

Yes. ask joins Cisco Meraki Dashboard API to NetSuite or HubSpot CRM on the same customer and returns the answer rather than every row. Cisco Meraki Dashboard API maps crm.company, which 227 other connectors also map.

Does actionlake keep my Cisco Meraki Dashboard API data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Cisco Meraki Dashboard API credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Cisco Meraki Dashboard API

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Cisco Meraki Dashboard API; the name is the vendor's own. Counts are from the Cisco Meraki Dashboard API service file, version 1.0.0.

Give your agent Cisco Meraki Dashboard API today.

Connect Cisco Meraki Dashboard API freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.