SaaSus Docs MCP Server
OfficialServer 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 | {} |
| logging | {
"enabled": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| saasusDocsSearchToolA | Search SaaSus Platform documentation to find relevant article URLs. Use this tool first to find relevant articles, then use saasus-docs-get-content tool to fetch the full content of specific articles. |
| saasusDocsContentToolA | Fetch the full content of a SaaSus Platform documentation article from its URL. Use this tool after getting URLs from saasus-docs-search-urls tool or saasus-docs-sitemap tool to retrieve the complete article content. |
| saasusDocsSitemapToolA | Fetch the sitemap XML from SaaSus Platform documentation to get a list of all available URLs. Useful for discovering all documentation pages and their structure, especially when search doesn't return relevant results or you need to browse the complete site hierarchy. Use with saasus-docs-get-content tool to fetch specific article content. |
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 3 tools
Each tool has a distinct role: search finds relevant article URLs, sitemap exposes all available URLs, and content retrieves the article body. Even though search and sitemap both return URLs, their purposes are clearly separated by the descriptions.
The exposed tool names follow a similar camelCase prefix pattern, but the descriptions reference different tool names like `saasus-docs-get-content` and `saasus-docs-search-URLs`, which do not match the provided tool names. This creates real ambiguity between the displayed names and how the tools describe their own workflows.
Three tools is an appropriate size for this documentation server: search, sitemap, and content retrieval cover the necessary operations without adding unnecessary surface area. The scope is narrow enough that each tool clearly earns its place.
The toolset covers the full documentation lifecycle: discover via search, enumerate via sitemap, then fetch content by URL. There are no obvious missing operations for a documentation-focused MCP server.