Skip to main content
Glama
SaaSus Docs MCP Server

SaaSus Docs MCP Server

Official

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-server

2. 依存関係のインストールとビルド

プロジェクトのルートディレクトリで以下のコマンドを実行してください。

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 node

server.jsのパスを確認:

realpath server.js

Claude 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.js

Cursorでの設定

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 tools
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.

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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables 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.
      3
      Apache 2.0
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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.
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      3
      7 npm
      MIT