SaaSus Docs MCP Server
OfficialRelated Servers
Alternatives to SaaSus Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides access to microCMS documentation, enabling AI assistants to search and retrieve the latest document content.3122 npm8MIT
- AlicenseAqualityDmaintenanceProvides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.36 npmMIT
- AlicenseAqualityNot gradedmaintenanceEnables users to access, search, and get recommendations from AWS documentation through natural language queries. Supports both global AWS documentation and AWS China documentation with tools to fetch pages, search content, and discover related resources.3Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceEnables querying and retrieving webpage content from websites by parsing sitemap.xml files and fetching HTML content from specified URLs. Includes rate limiting protection and supports listing all available pages from a sitemap.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables querying and retrieving webpage content from websites by parsing sitemap.xml files and fetching HTML content from specified URLs. Includes built-in rate limiting for responsible web scraping.-
- AlicenseNot gradedqualityCmaintenanceEnables searching and fetching Claude and Anthropic documentation with intelligent relevance scoring, optimized for MCP development, APIs, and examples.10 npm6MIT
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.