scm-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCM_TSG_ID | Yes | SCM tenant service group ID | |
| SCM_BASE_URL | No | Base URL for SCM API (default: https://api.strata.paloaltonetworks.com) | https://api.strata.paloaltonetworks.com |
| SCM_CLIENT_ID | Yes | SCM client ID | |
| SCM_CLIENT_SECRET | Yes | SCM client secret |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_addressesC | List address objects |
| list_address_groupsC | List address group objects |
| list_servicesC | List service objects |
| list_service_groupsC | List service group objects |
| list_tagsC | List tag objects |
| get_addressB | Get an address object by ID |
| get_address_groupB | Get an address group by ID |
| get_serviceB | Get a service object by ID |
| get_service_groupA | Get a service group by ID |
| get_tagB | Get a tag object by ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct combination of object type and action (get vs list), leaving no ambiguity. The five object types are clearly separated.
All tool names follow a consistent 'verb_object' pattern with underscores, using 'get_' for single retrieval and 'list_' for bulk retrieval, all lowercase.
10 tools covering five object types with two operations each is well-scoped for a read-only interface, fitting the typical 3-15 range.
Only read operations are provided; missing create, update, and delete tools severely limits the ability to manage objects, making the surface incomplete for a full management scenario.