Which integrations are available for this server?

Allows AI coding assistants to query the public Quasar Store documentation in real time, including listing all documentation products, searching by keyword, and reading full article content.

How do I use Quasar Store Docs MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Quasar Store Docs MCP search for payment gateway setup" 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.

Quasar Store Docs MCP

by iiamdark

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Remote

Quasar Store Docs MCP

An open-source MCP (Model Context Protocol) server that lets AI coding assistants query the public Quasar Store documentation in real time.

Fully compatible with Claude Desktop, Claude Code, Antigravity (Google), OpenCode, VS Code (via Cline, Continue, or Copilot MCP), Cursor, and any MCP-compatible client.

By default, the server is pre-configured to work with the live Quasar Store documentation — no environment variables or additional setup required.

Related MCP server: Documentation Retrieval MCP Server (DOCRET)

Tools

Tool	Type	Description
`list_docs`	Discovery	Lists all documentation products with article counts, overview URLs, and section names. No arguments needed.
`search_docs`	Search	Searches documentation by keyword. Returns matching article titles, URLs, and snippets.
`read_doc`	Read	Fetches full article content as formatted Markdown. Accepts a URL or relative path.

How It Works

The server connects to https://www.quasar-store.com/docs and extracts documentation content by scraping the public HTML pages.

The Quasar Store documentation is built with Next.js and uses React Server Components (RSC). The server handles this with a three-layer strategy:

Scans the raw HTML for all /docs/... links embedded in the RSC payload, building a complete index of every documentation article (40+ products, each with multiple sub-pages).
Extracts article content from the RSC data using a best-effort text parser that pulls out headings, paragraphs, and code blocks. If the RSC method fails, it falls back to traditional cheerio DOM extraction.
As a last resort, it returns the article title, meta description, and a list of related documentation links so the AI still receives useful navigation.

The server communicates with your AI client via stdio (standard input/output) using the JSON-RPC protocol — no HTTP server, no open ports, no network configuration needed.

Requirements

Node.js >= 18
npm (comes with Node.js)

Installation

You have two options:

Option A: Install via npx (recommended — no clone needed)

The package is published on npm, so you can run it directly without cloning or installing:

npx -y quasar-store-docs-mcp

Then in your MCP client configs, just reference npx as the command:

{
  "command": "npx",
  "args": ["-y", "quasar-store-docs-mcp"]
}

Note: -y tells npx to auto-confirm the install. Omit it if you want a confirmation prompt.

Option B: Clone and build locally

git clone https://github.com/iiamdark/quasar-docs-mcp.git
cd quasar-docs-mcp
npm install
npm run build
npm link                    # makes `quasar-store-docs-mcp` available globally

To verify the link worked:

which quasar-store-docs-mcp   # macOS / Linux
where quasar-store-docs-mcp   # Windows

You should see a path like /usr/local/bin/quasar-store-docs-mcp or C:\Users\...\npm\quasar-store-docs-mcp.

Configuration

The server works out of the box with https://www.quasar-store.com as the documentation base. You do not need to set any environment variables.

Environment Variable (optional)

To point the server at a different documentation site:

# macOS / Linux
export DOCS_BASE_URL="https://your-docs-site.com"

# Windows (Command Prompt)
set DOCS_BASE_URL=https://your-docs-site.com

# Windows (PowerShell)
$env:DOCS_BASE_URL = "https://your-docs-site.com"

If not set, the server defaults to https://www.quasar-store.com.

CSS Selectors

If you are using the server with a different documentation site, you may need to adjust the CSS selectors in src/index.ts:

const SELECTORS = {
  article: "article, .doc-content, .markdown-body, main, .docs-content-page",
  title: "h1",
  navLinks: "nav a, .sidebar a, .toc a, aside a",
};

Client Integration

You have three options for referencing the server in your MCP client configuration:

Option A (recommended — no install): Use npx -y quasar-store-docs-mcp — works without cloning or building
Option B: Use the global command quasar-store-docs-mcp (after running npm link)
Option C: Use the full path to build/index.js directly

Claude Desktop

Configuration file: claude_desktop_config.json

Option A — with npx (no install needed):

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "npx",
      "args": ["-y", "quasar-store-docs-mcp"]
    }
  }
}

Option B — with npm link:

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "quasar-store-docs-mcp"
    }
  }
}

Option C — with direct path:

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "node",
      "args": ["/full/path/to/quasar-docs-mcp/build/index.js"]
    }
  }
}

Claude Code

# Option A — with npx:
claude mcp add quasar-store-docs -- npx -y quasar-store-docs-mcp

# Option B — with npm link:
claude mcp add quasar-store-docs -- quasar-store-docs-mcp

# Option C — with direct path:
claude mcp add quasar-store-docs -- node /full/path/to/quasar-docs-mcp/build/index.js

Antigravity (Google)

Antigravity reads MCP server configurations from ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (per-project).

Option A — with npx (no install needed):

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "npx",
      "args": ["-y", "quasar-store-docs-mcp"]
    }
  }
}

Option B — with npm link or locally built:

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "quasar-store-docs-mcp"
    }
  }
}

After saving:

Restart Antigravity, or
Open the agent sidebar → click ... → MCP Servers → Manage MCP Servers → the server should appear in the list.

OpenCode

OpenCode uses a configuration file at ~/.config/opencode/opencode.json. The format is different from other clients:

Option A — with npx:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quasar-store-docs": {
      "type": "local",
      "command": ["npx", "-y", "quasar-store-docs-mcp"],
      "enabled": true
    }
  }
}

Option B — with npm link:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quasar-store-docs": {
      "type": "local",
      "command": ["quasar-store-docs-mcp"],
      "enabled": true
    }
  }
}

Differences from other clients: OpenCode uses "mcp" (not "mcpServers"). The command field is an array. Each server requires "type": "local" and "enabled": true.

VS Code (Cline, Continue, Copilot)

Option A — with npx:

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "npx",
      "args": ["-y", "quasar-store-docs-mcp"]
    }
  }
}

Option B — with npm link or locally built:

{
  "mcpServers": {
    "quasar-store-docs": {
      "command": "quasar-store-docs-mcp"
    }
  }
}

Cursor

Option A — with npx:

Name: quasar-store-docs
Type: command
Command: npx -y quasar-store-docs-mcp

Option B — with npm link:

Name: quasar-store-docs
Type: command
Command: quasar-store-docs-mcp

Tools Quick Reference

`list_docs` — Browse available documentation

Lists every product/category indexed from the Quasar Store docs (93 products total).

Signature:

list_docs()

No arguments needed.

Example output (truncated):

Available documentation categories (93 total):

### Advanced Inventory
Articles: 6 | Overview: https://www.quasar-store.com/docs/advanced-inventory
Sections: Commands And Exports, Convert Inventory Items, General Integrations, How To Create Missions, Installation, Item Configuration

### Housing Creator
Articles: 4 | Overview: https://www.quasar-store.com/docs/housing-creator
Sections: Commands And Exports, Installation, Inventory Items

### Smartphone
Articles: 5 | Overview: https://www.quasar-store.com/docs/smartphone
Sections: Commands And Exports, How To Install Apps, Installation
...

When to use: When you don't know what documentation exists. Start here to discover products, then search or read specific articles.

`search_docs` — Find articles by keyword

Searches article titles and URLs for a query term.

Signature:

search_docs(query: string)

Argument	Type	Description
`query`	string (required)	Search term. Matches against article titles and URLs. Case insensitive.

Good queries: "installation", "database errors", "advanced inventory", "commands", "exports", "common issues"

Example output:

Results for "installation":

1. **Smartphone — Installation**
   URL: https://www.quasar-store.com/docs/smartphone/installation
   Documentation: Smartphone — Installation

2. **Advanced Inventory — Installation**
   URL: https://www.quasar-store.com/docs/advanced-inventory/installation
   Documentation: Advanced Inventory — Installation

3. **Police Creator — Installation**
   URL: https://www.quasar-store.com/docs/police-creator/installation
   Documentation: Police Creator — Installation

When to use: When you know roughly what you're looking for. The search covers article titles and URLs, so use specific keywords.

No results? The tool returns the first 15 available articles as a fallback, so the AI can still see what exists.

`read_doc` — Read full article content

Fetches a documentation article and returns it as formatted Markdown.

Signature:

read_doc(url: string)

Argument	Type	Description	Examples
`url`	string (required)	Full URL or relative path. The server resolves relative paths against the base URL.	`"advanced-inventory/installation"` `"https://www.quasar-store.com/docs/smartphone/installation"` `"housing-creator/commands-and-exports"`

Example output:

# Installation

> Installation guide — please follow each step carefully and exactly as described to ensure the script works correctly on your server.

---

Download the script assets from the Cfx.re portal...

## Step 1: Download

Open the Cfx.re granted assets page...

## Step 2: Add to server

Place the folder in your `resources` directory...

---
Source: https://www.quasar-store.com/docs/advanced-inventory/installation

What gets extracted:

Article title and meta description
Section headings (converted to Markdown # / ## / ###)
Paragraphs of explanatory text
Code blocks
Lists (bulleted and numbered)
Tables (converted to Markdown table format)
Blockquotes

When to use: After finding an article via list_docs or search_docs. Pass the URL or relative path to get the full content.

Usage Examples

Once configured, your AI assistant will automatically discover the 3 available tools and use them when relevant. Here are typical interaction patterns:

Pattern: Discover → Search → Read

This is the most common workflow:

Step	Trigger	Tool called
1	"What documentation exists for housing?"	`list_docs()` → finds "Housing Creator"
2	"How do I install it?"	`search_docs("housing creator installation")` → finds the installation article
3	"Read it to me"	`read_doc("housing-creator/installation")` → returns full content

Conversation examples

You ask...	The AI calls...	Result
"What documentation is available?"	`list_docs()`	Full product listing with 93 categories
"How do I install Advanced Inventory?"	`search_docs("advanced inventory installation")`	Links to installation guides
"What are common database errors?"	`search_docs("database errors")`	Troubleshooting articles
"Explain the housing creator features"	`search_docs("housing creator")` + `read_doc(...)`	Full article content
"Read me the smartphone commands"	`read_doc("smartphone/commands-and-exports")`	Commands in Markdown
"What sections does Admin Menu have?"	`list_docs()` → find "Admin Menu" in output	Section listing for Admin Menu

Project Structure

quasar-docs-mcp/
│
├── src/
│   └── index.ts              # MCP server implementation
│
├── build/                    # Compiled JavaScript output (generated)
│
├── banner.png                # README banner image
├── package.json              # Dependencies, scripts, and metadata
├── tsconfig.json             # TypeScript compiler configuration
└── README.md                 # This file

Key files explained

File	Purpose
`src/index.ts`	Complete MCP server: initializes the server, registers `list_docs`, `search_docs`, and `read_doc` tools, implements web scraping with axios + cheerio, handles RSC payload extraction for Next.js sites, and includes an in-memory cache with TTL
`package.json`	Project metadata, dependencies (`@modelcontextprotocol/sdk`, `axios`, `cheerio`, `zod`), build scripts
`tsconfig.json`	TypeScript configuration targeting ES2022 with Node16 module resolution
`build/index.js`	Compiled output — this is what you reference in your MCP client configs

Troubleshooting

"Command not found: quasar-store-docs-mcp"

You have not run npm link, or the npm global bin directory is not in your PATH.

Run npm link from the project directory
Or use the full path to build/index.js in your client config

Server starts but tools return errors

Check that https://www.quasar-store.com is accessible from your network
Try setting a different DOCS_BASE_URL if you are using a custom documentation site

"Article not found (404)"

Make sure the URL or path is correct
Relative paths should be relative to the docs base URL (e.g. advanced-inventory/installation)
You can always use a full URL directly

Content extraction returns mostly empty

The Quasar Store docs site uses Next.js with client-side rendering for some content. The server tries multiple extraction strategies (RSC → cheerio → related links). If all fail, the AI will still receive the article title, description, and navigation links to related articles.

License

MIT License

Copyright (c) 2026 iiamdark

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Built with Model Context Protocol — an open standard for connecting AI assistants with tools and data.

Available Tools

3 tools

list_docsA

List all available documentation products/categories with article counts and section overviews

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description fully carries the burden. It clearly indicates a read-only operation by using 'list'. It does not mention side effects, rate limits, or performance, but for a simple list tool with no params, this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words. It is front-loaded with the purpose and efficiently conveys the scope and content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description adequately covers what the tool returns (products/categories with counts and overviews). It gives a good high-level understanding, though a more explicit format detail would be ideal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so schema coverage is trivially 100%. The description adds meaning beyond the schema by specifying the output includes article counts and section overviews. Baseline for no params is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists 'all available documentation products/categories' with 'article counts and section overviews'. The verb 'list' is specific, and the resource is well-defined. It distinguishes from siblings 'search_docs' and 'read_doc' which are for searching and reading specific docs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when an overview of docs is needed, but does not explicitly state when not to use it or provide alternatives. Sibling tools suggest differentiation but no explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

read_docA

Read the full content of a Quasar Store documentation article by its URL or relative path

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes	Full article URL or relative path (e.g. "advanced-inventory/installation" or "https://www.quasar-store.com/docs/advanced-inventory/installation")

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

For a read-only operation with no annotations, the description transparently indicates it retrieves full content. No side effects or behavioral nuances beyond reading are expected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words, clearly front-loaded with the action and object.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple read tool with one parameter and no output schema; no further information is needed for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description reinforces the parameter's flexibility (URL or path) and adds the return value nature ('full content'), going slightly beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool reads the full content of a documentation article using a URL or relative path. Distinct from sibling tools list_docs and search_docs which list and search respectively.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Comments imply use when a specific article URL is available, but no explicit when-to-use or when-not-to-use guidance, nor comparisons to alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_docsB

Search Quasar Store documentation articles by a query term

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Search term, e.g. 'installation', 'database errors', 'advanced inventory'

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description only mentions searching by query term. It does not disclose behavioral traits such as output format, pagination, or whether it is read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no extraneous information. It is concise and front-loaded, but could benefit from a slightly more structured format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no output schema, the description is minimal. It does not explain what kind of results are returned or any limitations such as maximum results or ordering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already includes a detailed description with examples. The tool description adds no further parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'Search' and the resource 'Quasar Store documentation articles', which effectively distinguishes it from sibling tools 'list_docs' and 'read_doc'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'list_docs' or 'read_doc'. The description only states what it does, without providing decision context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv1.0.2Jul 28, 2026
- First observedlist_docs
- First observedread_doc
- First observedsearch_docs

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored 2026-07-28 08:11 across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: listing an overview, searching content, and reading a specific article. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case: list_docs, search_docs, read_doc. No deviations.

Tool Count4/5

Three tools is a reasonable size for a documentation server, covering the core needs of listing, searching, and reading. It could potentially be expanded with more granular navigation tools, but the count is appropriate.

Completeness4/5

The tool set covers the essential operations for a read-only documentation server: browse overview, search, and retrieve full content. Minor gaps exist, such as listing articles within a specific category, but the primary workflows are supported.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

gread A
io.github.NitroRCr
An MCP server that gives your AI access to the source code and docs of all public github repos
Version Control Code Analysis Documentation Access
5361
driflyte-mcp-server
com.driflyte
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Search Web Scraping Knowledge & Memory
211
mcp
dev.augments
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Developer Tools Documentation Access
2128
docs
dev.continue
An MCP server for docs.continue.dev
Documentation Access Developer Tools Search
2

Related MCP Servers

Vibe Coder MCP
Developer Tools Code Execution Autonomous Agents
freshtechbro
A
license
B
quality
C
maintenance
An MCP server that supercharges AI assistants with powerful tools for software development, enabling research, planning, code generation, and project scaffolding through natural language interaction.
Updated a year ago (2025-08-21 03:06 UTC)
11
32
103
MIT
Documentation Retrieval MCP
Documentation Access Developer Tools RAG Systems
Sreedeep-SS
A
license
Not graded
quality
D
maintenance
An MCP server that enables AI assistants to access up-to-date documentation for Python libraries like LangChain, LlamaIndex, and OpenAI through dynamic fetching from official sources.
Updated a year ago (2025-03-22 22:00 UTC)
1
MIT
Dedalus MCP Documentationofficial
Documentation Access Search RAG Systems
dedalus-labs
A
license
A
quality
D
maintenance
An MCP server that serves documentation and enables AI-powered search, Q\&A, and document analysis for developer tools and guides.
Updated a year ago (2025-09-20 12:06 UTC)
5
4
MIT
Aindreyway MCP Codex Keeper
Documentation Access Developer Tools
AshutoshBuilds
A
license
A
quality
D
maintenance
An intelligent MCP server that serves as a guardian of development knowledge, providing AI assistants with curated access to latest documentation and best practices.
Updated 2 years ago (2024-12-20 05:12 UTC)
4
506
MIT

Quasar Store Docs MCP

Table of Contents

Tools

How It Works

Requirements

Installation

Option A: Install via npx (recommended — no clone needed)

Option B: Clone and build locally

Configuration

Environment Variable (optional)

CSS Selectors

Client Integration

Claude Desktop

Claude Code

Antigravity (Google)

OpenCode

VS Code (Cline, Continue, Copilot)

Cursor

Tools Quick Reference

list_docs — Browse available documentation

search_docs — Find articles by keyword

read_doc — Read full article content

Usage Examples

Pattern: Discover → Search → Read

Conversation examples

Project Structure

Key files explained

Troubleshooting

"Command not found: quasar-store-docs-mcp"

Server starts but tools return errors

"Article not found (404)"

Content extraction returns mostly empty

License

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Vibe Coder MCP

Documentation Retrieval MCP

Dedalus MCP Documentationofficial

Aindreyway MCP Codex Keeper

`list_docs` — Browse available documentation

`search_docs` — Find articles by keyword

`read_doc` — Read full article content