> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mcp-b.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Project metadata

> MCP endpoint, files, versioning policy, and changelog for WebMCP packages.

## Docs MCP endpoint

The documentation site exposes an MCP server at:

```text title="MCP endpoint" theme={null}
https://docs.mcp-b.ai/mcp
```

This endpoint is provided by Mintlify and serves the published documentation content. It supports the [Model Context Protocol](https://modelcontextprotocol.io) over HTTP.

### Direct URL (streamable HTTP)

Clients that accept an MCP server URL directly:

```text title="MCP server URL" theme={null}
https://docs.mcp-b.ai/mcp
```

### Command-based (stdio via mcp-remote)

Clients that require a command and arguments:

```json theme={null}
{
  "mcpServers": {
    "WebMCP Docs": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.mcp-b.ai/mcp"]
    }
  }
}
```

### Setup by client

<AccordionGroup>
  <Accordion title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http "WebMCP Docs" "https://docs.mcp-b.ai/mcp"
    ```
  </Accordion>

  <Accordion title="Claude Desktop">
    1. Open **Settings** then **Connectors**.
    2. Click **Add custom connector**.
    3. Set the name to "WebMCP Docs" and the URL to `https://docs.mcp-b.ai/mcp`.
    4. Click **Save**, then **Connect**.
  </Accordion>

  <Accordion title="Cursor">
    Add to `.cursor/mcp.json` in your project root:

    ```json theme={null}
    {
      "mcpServers": {
        "WebMCP Docs": {
          "url": "https://docs.mcp-b.ai/mcp"
        }
      }
    }
    ```

    Restart Cursor after saving.
  </Accordion>

  <Accordion title="Windsurf">
    Add to `mcp_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "WebMCP Docs": {
          "command": "npx",
          "args": ["mcp-remote", "https://docs.mcp-b.ai/mcp"]
        }
      }
    }
    ```

    Restart Windsurf after saving.
  </Accordion>

  <Accordion title="ChatGPT">
    <Note>MCP support in ChatGPT requires a paid plan with Developer Mode enabled.</Note>

    1. Enable **Developer Mode** in ChatGPT settings.
    2. Go to **Settings**, then **Connectors**.
    3. Click **Add MCP server**.
    4. Enter `https://docs.mcp-b.ai/mcp` as the server URL.
    5. Name it "WebMCP Docs" and click **Save**.
  </Accordion>

  <Accordion title="Codex">
    Add to `~/.codex/config.toml`:

    ```toml theme={null}
    [mcp_servers.webmcp_docs]
    command = "npx"
    args = ["-y", "mcp-remote", "https://docs.mcp-b.ai/mcp"]
    ```

    Restart Codex after saving.
  </Accordion>
</AccordionGroup>

### What the server provides

The MCP server gives connected agents read access to the full documentation site. Agents can search for pages, retrieve page content, and browse the site structure.

***

## llms.txt

The documentation site serves two files that follow the [llmstxt.org](https://llmstxt.org)
convention for AI-readable site indexing.

### Files

| File | URL | Contents |
| - | - | - |
| `llms.txt` | [docs.mcp-b.ai/llms.txt](https://docs.mcp-b.ai/llms.txt) | Maintained index of key documentation and upstream sources |
| `llms-full.txt` | [docs.mcp-b.ai/llms-full.txt](https://docs.mcp-b.ai/llms-full.txt) | Full rendered content of published pages, generated by Mintlify |

### How they are maintained

The repository owns `apps/documentation-website/llms.txt`. Mintlify serves that
root-level file instead of its generated short index. Keep it concise and update
it when canonical sources or primary routes change. See Mintlify's
[custom file behavior](https://www.mintlify.com/docs/ai/llmstxt#custom-files).

Mintlify generates `llms-full.txt` from the published pages on each deployment.
It contains each page's Markdown export, separated by page headers.

The maintained `llms.txt` includes:

* The proposal status and `document.modelContext` surface
* Canonical Community Group, Chrome, OpenAI, and WPT sources
* Entry points for tutorials, how-to guides, explanations, and package references
* Links to the full Markdown export, MCP endpoint, and source repository

### Usage

AI assistants (Claude, ChatGPT, Gemini, Perplexity, and others) fetch `llms.txt` to understand what the site covers before retrieving specific pages. If your agent supports URL-based context, point it at `https://docs.mcp-b.ai/llms.txt`.

The MCP endpoint and `llms.txt` serve different purposes. `llms.txt` is a static file that agents fetch over plain HTTP. The MCP endpoint is an interactive server that agents connect to as an MCP client, allowing structured queries against the documentation.

***

## Versioning and changelog

WebMCP uses [Changesets](https://github.com/changesets/changesets) for versioning. The browser packages share one fixed release version. Changesets bumps the full group when any member changes. Private apps, templates, and test packages are not published.

### Where to find changelogs

| Source | What it covers |
| - | - |
| [GitHub Releases](https://github.com/WebMCP-org/npm-packages/releases) | Per-release notes with links to PRs and commits |
| [npm version history](https://www.npmjs.com/package/@mcp-b/global?activeTab=versions) | Published versions for any `@mcp-b/*` package |
| Git log (`chore(release): version packages`) | Changeset-generated version bumps in the monorepo |

### Versioning policy

All packages follow [Semantic Versioning](https://semver.org/):

| Increment | Meaning |
| - | - |
| Major (X.0.0) | Breaking API changes |
| Minor (X.Y.0) | New features, backward compatible |
| Patch (X.Y.Z) | Bug fixes, backward compatible |

### Package scope

The fixed release train contains these browser packages:

| Package | Purpose |
| - | - |
| `@mcp-b/global` | Entry point, auto-initializes polyfill and server |
| `@mcp-b/webmcp-polyfill` | Polyfills `document.modelContext` |
| `@mcp-b/webmcp-ts-sdk` | BrowserMcpServer with MCP extensions |
| `@mcp-b/webmcp-types` | Compatibility alias for upstream `webmcp-types` |
| `@mcp-b/react-webmcp` | React hooks for tool registration |
| `usewebmcp` | Tool-only React hook |
| `@mcp-b/transports` | Tab and iframe transports |
| `@mcp-b/mcp-iframe` | Iframe MCP communication |
| `@mcp-b/webmcp-extension` | MV3 extension template and isolated-world client |
| `@mcp-b/smart-dom-reader` | DOM content extraction |
| `@mcp-b/smart-dom-reader-server` | Node MCP server wrapping the reader |
| `@mcp-b/webmcp-local-relay` | Local relay server for desktop agents |

See the [package index](/packages/index) for package-specific documentation.

### Reporting issues

If you find a bug or regression after upgrading:

1. Check [existing issues](https://github.com/WebMCP-org/npm-packages/issues).
2. Open a [new issue](https://github.com/WebMCP-org/npm-packages/issues/new) with the package name, version numbers, steps to reproduce, and expected versus actual behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.