Cloudscape 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
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cloudscape_search_docsA | Search the Cloudscape documentation index for relevant files. Use this tool FIRST to find the correct file paths. It returns a list of files with their relevance scores. It does NOT return the full content. Args: query: The search term (e.g., "collection preferences", "table sorting props"). Returns: A concise list of relevant files and their paths. |
| cloudscape_read_docA | Read the FULL content of a documentation file. Use this tool SECOND, after finding the correct path via 'cloudscape_search_docs'. Args: file_path: The exact path provided by the search tool (e.g., "docs/components/button.md"). |
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 2 tools
The two tools have completely distinct purposes: one searches for relevant files, the other reads a specific file's content. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun pattern with a consistent prefix: 'cloudscape_search_docs' and 'cloudscape_read_doc'. The naming is predictable and clear.
With only two tools, the set feels thin but is reasonable for a documentation search and read workflow. It is minimal yet sufficient for the stated purpose.
The core workflow of searching and reading documentation is fully covered. A minor gap is the lack of a way to list all documents or browse by category, but agents can typically work around this via search.