Schema | Panorama MCP Server

Panorama MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`PANORAMA_URL`	Yes	The base URL of the Panorama management interface. Example: https://panorama.example.net
`PANORAMA_API_KEY`	Yes	API key for a dedicated read-only Panorama administrator or service account. Must be kept secret.
`PANORAMA_RULEBASE`	Yes	The rulebase to evaluate, e.g., 'pre-rulebase'.
`PANORAMA_VERIFY_TLS`	Yes	Whether to enable TLS certificate verification. Set to 'false' only in controlled lab environments; do not disable in production.	true
`PANORAMA_DEVICE_GROUP`	Yes	The Panorama device group to use, e.g., 'shared'.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
list_device_groupsA	List Panorama device groups visible to the configured read-only API key.
get_security_rulesB	Fetch normalized security rules from one Panorama device group and rulebase.
search_policy_coverageA	Find exact duplicates, coverage, conflicts, and partial overlaps without changing Panorama.
preclear_rule_requestB	Run deterministic read-only preclear checks before a rule change is considered.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fquiroga/panorama-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server