prisma-cloud-docs-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_prisma_docsC | Search Prisma Cloud documentation |
| search_prisma_api_docsC | Search Prisma Cloud API documentation |
| search_all_docsC | Search across all Prisma Cloud documentation sites. |
| index_prisma_docsA | Index Prisma Cloud documentation. Call this first before searching. |
| index_prisma_api_docsA | Index Prisma Cloud API documentation. Call this first before searching. |
| get_index_statusA | Check how many documents are currently cached. |
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 6 tools
The tools have some overlap that could cause confusion, particularly between the three search tools (search_all_docs, search_prisma_api_docs, search_prisma_docs) and the two index tools (index_prisma_api_docs, index_prisma_docs). However, the descriptions clarify the scope of each, helping to distinguish them. The get_index_status tool is clearly distinct in purpose.
All tool names follow a consistent verb_noun pattern with snake_case throughout, such as get_index_status, index_prisma_api_docs, and search_all_docs. This predictability makes it easy for agents to understand and use the tools without confusion.
With 6 tools, the server is well-scoped for its purpose of indexing and searching Prisma Cloud documentation. Each tool serves a clear function, and the count is neither too sparse nor overwhelming, fitting typical expectations for a documentation-focused MCP server.
The tool set covers the core workflows of indexing and searching documentation, with separate tools for API and general docs, plus a status check. A minor gap is the lack of tools for managing or updating indexed content, but agents can work around this by re-indexing as needed.