Click on "Install 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は、Model Context Protocol (MCP) サーバーとして動作し、SaaSus Platformのドキュメント検索機能をClaude DesktopやCursorなどのMCP互換クライアントから利用できるようにします。
Node.js（v22推奨）
npm（Nodeに含まれています）
Related MCP server: Webpage MCP Server
以下のコマンドでプロジェクトをクローンしてください。
git clone https://github.com/saasus-platform/saasus-docs-mcp-server.git
cd saasus-docs-mcp-serverプロジェクトのルートディレクトリで以下のコマンドを実行してください。
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を開き、「設定」→「開発者」→「構成を編集」からサーバー設定を追加してください。
{
"mcpServers": {
"saasus-docs": {
"command": "/path/to/node",
"args": [
"/path/to/server.js"
]
}
}
}設定後、Claude Desktopを再起動してください。
Claude CodeのCLIを使用して、以下のコマンドでMCPサーバーを登録できます。
claude mcp add --scope user saasus-docs-mcp-server /path/to/node /path/to/server.jsCursorの設定を開き、「MCP」セクションに移動してください。
以下の設定を追加してください。
{
"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ツールで記事の詳細内容を取得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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL of the SaaSus Platform documentation article to fetch |
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| title | Yes | |
| content | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It states 'fetch' implying a read-only operation, but does not disclose additional details like authentication requirements, rate limits, or whether content is cached. While not misleading, it is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the core action, and every sentence adds value. There is no redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one required parameter, output schema exists), the description is complete. It covers what the tool does, when to use it, and refers to sibling tools for URL retrieval.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description mentions the URL parameter but adds no extra meaning beyond what the schema already provides. The description does not clarify format or constraints (e.g., must be a valid SaaSus URL).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Fetch the full content') and the specific resource ('SaaSus Platform documentation article from its URL'). It distinguishes from sibling tools by mentioning that it is used after getting URLs from the search or sitemap tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit guidance is provided: 'Use this tool after getting URLs from saasus-docs-search-urls tool or saasus-docs-sitemap tool.' This tells the agent exactly when to invoke this tool relative to its siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query to find relevant SaaSus Platform documentation |
| Name | Required | Description |
|---|---|---|
| query | Yes | |
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It states the tool returns 'relevant article URLs' but does not disclose search result format, limits, ordering, or pagination. Adequate but incomplete for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first states purpose, second provides sequential workflow guidance. No redundant information; every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, output schema present), the description adequately informs the agent of the search-primary-then-fetch-content workflow. Could not be considered incomplete for its complexity level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage for the single 'query' parameter. Description adds no extra meaning beyond 'search query' already in schema. Baseline score is appropriate as schema already documents the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Search SaaSus Platform documentation to find relevant article URLs', identifying the verb, resource, and outcome. Distinguishes from siblings by specifying this tool is used first to locate articles before fetching content.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises to use this tool first, then follow with 'saasus-docs-get-content tool to fetch the full content of specific articles', providing clear sequential guidance. Does not mention when to avoid or alternative scenarios but covers main use case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| baseUrl | Yes | |
| structure | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description states it fetches sitemap XML, a read operation, but does not detail output format or any side effects. Output schema exists, slightly reducing burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences, each adding value: action, use case, and tool combination. No redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Sufficient for a no-parameter tool with output schema. Provides purpose and usage context, though could mention that output is XML sitemap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; baseline score of 4 is appropriate. No additional parameter info needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it fetches the sitemap XML from SaaSus Platform documentation to list all available URLs, distinguishing it from search and content tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides when to use: when search fails or need complete site hierarchy. Also suggests combining with content tool, but lacks explicit when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
saasusDocsContentToolsaasusDocsSearchToolsaasusDocsSitemapToolEach tool has a clearly distinct purpose: search finds relevant articles, sitemap lists all URLs, and content fetches full article text. There is no overlap in functionality, and the descriptions explicitly guide agents on when to use each tool.
The naming follows a consistent pattern with a 'saasusDocs' prefix and descriptive suffixes (ContentTool, SearchTool, SitemapTool). However, the descriptions refer to slightly different names (e.g., 'saasus-docs-get-content' vs. 'saasusDocsContentTool'), which is a minor deviation.
With 3 tools, this server is well-scoped for its documentation domain. Each tool serves a specific, essential function (search, browse, retrieve) without redundancy, making the count appropriate and efficient for the purpose.
The tool set provides complete coverage for accessing documentation: search for discovery, sitemap for browsing, and content for retrieval. There are no obvious gaps, as these tools cover the full lifecycle from finding to reading articles.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Web search, URL content extraction to Markdown, site mapping, and recursive web crawler.
Jina AI Reader/Search MCP — turn any URL into clean LLM-ready markdown, plus web search.
Help center for SaaS teams. 14-tool MCP server for articles, collections, and search.
Query any docs site via MCP. Submit a URL, ask questions, get cited answers.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/saasus-platform/saasus-docs-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
