Cisco Meraki MCP integration for AI agents.
Connect AI agents to Cisco Meraki through 4 structured actions, including get device, list organization inventory devices, and list organization networks. Re…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Cisco Meraki integration exposes
The Cisco Meraki Agent App exposes 4 provider-backed actions for developer tools and security work. Its current contract lets an authorized agent retrieve one meraki device by serial number, list inventory devices in a meraki organization with simple search filters, and list networks that the api key can access in a meraki organization. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Cisco Meraki account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cisco Meraki capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_deviceREADRetrieve one Meraki device by serial number.
INPUTS: serial
list_organization_inventory_devicesREADList inventory devices in a Meraki organization with simple search filters.
INPUTS: organizationId / perPage / startingAfter / endingBefore / usedState
list_organization_networksREADList networks that the API key can access in a Meraki organization.
INPUTS: organizationId / configTemplateId / isBoundToConfigTemplate / tags / tagsFilterType
list_organizationsREADList the Meraki organizations available to the connected API key.
INPUTS: perPage / startingAfter / endingBefore
INPUT CONTRACTS
Know what the action needs before it runs.
get_device
serialREQUIRED- The Meraki device serial number.
list_organization_inventory_devices
organizationIdREQUIRED- The Meraki organization ID.
perPageOPTIONAL- The number of inventory devices to return on each page.
startingAfterOPTIONAL- The pagination token that starts the page after this value.
endingBeforeOPTIONAL- The pagination token that ends the page before this value.
usedStateOPTIONAL- Filter inventory by used or unused state.
list_organization_networks
organizationIdREQUIRED- The Meraki organization ID.
configTemplateIdOPTIONAL- Only return networks bound to this config template ID.
isBoundToConfigTemplateOPTIONAL- Only return networks by config-template binding state.
tagsOPTIONAL- Case-sensitive tags used to filter networks.
tagsFilterTypeOPTIONAL- How tag filters are matched.
list_organizations
perPageOPTIONAL- The number of organizations to return on each page.
startingAfterOPTIONAL- The pagination token that starts the page after this value.
endingBeforeOPTIONAL- The pagination token that ends the page before this value.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Device
Retrieve one Meraki device by serial number. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_deviceVerify with List Organization Inventory Devices
List inventory devices in a Meraki organization with simple search filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_organization_inventory_devicesSAFETY BOUNDARY
Operate Cisco Meraki with explicit limits
- Authorize Cisco Meraki with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Cisco Meraki data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Cisco Meraki rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Cisco Meraki task completed successfully.
CONNECTION MODEL
API key
Cisco Meraki Dashboard API key. Generate or manage personal API keys in the Meraki dashboard under Organization > API & Webhooks > API keys and access: https://developer.cisco.com/meraki/api-v1/authorization/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Cisco Meraki.