SaaSus Docs MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SaaSus Docs MCP Server search for authentication setup documentation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SaaSus Docs MCP Server
SaaSus Docs MCP Serverは、Model Context Protocol (MCP) サーバーとして動作し、SaaSus Platformのドキュメント検索機能をClaude DesktopやCursorなどのMCP互換クライアントから利用できるようにします。
前提条件
Node.js(v22推奨)
npm(Nodeに含まれています)
Related MCP server: Webpage MCP Server
インストール
1. リポジトリのクローン
以下のコマンドでプロジェクトをクローンしてください。
git clone https://github.com/saasus-platform/saasus-docs-mcp-server.git
cd saasus-docs-mcp-server2. 依存関係のインストールとビルド
プロジェクトのルートディレクトリで以下のコマンドを実行してください。
npm install
npm run buildビルドが完了すると、ルートディレクトリにserver.jsファイルが生成されます。
提供される機能
このMCPサーバーは以下のツールを提供します:
saasus-docs-search-urls: SaaSus Platformドキュメント内を検索し、関連記事のURLを取得
saasus-docs-get-content: 指定されたURLのSaaSus Platformドキュメント記事の完全なコンテンツを取得
saasus-docs-sitemap: SaaSus PlatformドキュメントのサイトマップからすべてのページのURL一覧を取得
設定前の準備
パスの確認
設定を行う前に、以下のコマンドで必要なパスを確認してください。
nodeのパスを確認:
which nodeserver.jsのパスを確認:
realpath server.jsClaude Desktopでの設定
Claude Desktopを開き、「設定」→「開発者」→「構成を編集」からサーバー設定を追加してください。
{
"mcpServers": {
"saasus-docs": {
"command": "/path/to/node",
"args": [
"/path/to/server.js"
]
}
}
}設定後、Claude Desktopを再起動してください。
Claude Code (CLI) での設定
Claude CodeのCLIを使用して、以下のコマンドでMCPサーバーを登録できます。
claude mcp add --scope user saasus-docs-mcp-server /path/to/node /path/to/server.jsCursorでの設定
1. 設定画面の表示
Cursorの設定を開き、「MCP」セクションに移動してください。
2. サーバー設定の追加
以下の設定を追加してください。
{
"mcpServers": {
"saasus-docs": {
"command": "/path/to/node",
"args": [
"/path/to/server.js"
]
}
}
}使用例
このMCPサーバーを使用することで、Claude DesktopやCursorから直接SaaSus Platformのドキュメントを検索・取得できます。
# SaaSus Platformの料金プランについて調べて
# → saasus-docs-search-urlsツールで関連記事を検索
# → saasus-docs-get-contentツールで記事の詳細内容を取得Available Tools
3 toolssaasusDocsContentToolA
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.
Inputs: url (required). Returns: url, title, content
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.
Inputs: query (required). Returns: query, results
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.
Inputs: no named parameters. Returns: baseUrl, structure
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Search and fetch tools over the pages of pournasserian.com, Amir Pournasserian's personal website: his writing on MCP, AI agents and RAG, his experience, case studies and open-source projects. No authentication. Runs the open-source mcp-my-site.
Search and read the Claude Platform documentation and API reference.
Find, write, publish and check pages and API references in your DeveloperHub docs from an AI client
Web search, URL content extraction to Markdown, site mapping, and recursive web crawler.
Related MCP Servers
- 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.-
- 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.37 npmMIT