---
title: "AI agents and MCP | Rigel CMS docs"
url: "https://rigelcms.dev/docs/mcp"
description: "Connect an AI agent to Rigel's public MCP endpoint for release information, GitHub sign-in setup and documentation links."
---

Rigel’s public Model Context Protocol (MCP) server gives AI agents release information, GitHub sign-in setup and links to the documentation. It uses Streamable HTTP and requires no authentication.

The endpoint returns public information only. It cannot access repositories or private content, edit content, or read or search the full documentation. To read a linked guide, your agent needs a separate web-fetch capability.

## Connect your agent

Add this endpoint in your client’s remote MCP server settings:

```
https://rigelcms.dev/mcp
```

For clients that accept a `mcpServers` configuration, the basic shape is:

```
{
  "mcpServers": {
    "rigel-docs": {
      "url": "https://rigelcms.dev/mcp"
    }
  }
}
```

Configuration shapes differ between clients. Select HTTP or Streamable HTTP if your client asks for a transport, and follow its instructions for where to put the configuration. The `rigel-docs` name is a local label you can change.

Opening the endpoint as a web page redirects to this guide; MCP clients use POST requests to the endpoint itself. Any compatible client can connect, regardless of provider or origin. Browser requests use public CORS without credentials; server-to-server clients need no Origin header.

## Available tools

| Tool | Arguments | Returns |
| --- | --- | --- |
| get_project_info | {} | Current release information, capabilities and public documentation, starter and source links. |
| get_auth_setup | {} | Public GitHub App setup URLs and requirements, including the optional provided authentication service. |

Both tools are read-only and take no arguments. Your MCP client can inspect their input schemas through `tools/list`. The [server discovery card](https://rigelcms.dev/.well-known/mcp/server-card.json) lists the endpoint, authentication requirement and tool names.

## Example prompt

```
Use Rigel's MCP tools to check the current release and GitHub sign-in
setup. Summarize the requirements and give me the relevant guide links.
If you have a separate web-fetch tool, read those linked guides before
suggesting configuration. Otherwise, tell me which guides to open.
```

You can also read the [documentation index](/docs/), [getting started guide](/docs/getting-started/) and [GitHub publishing guide](/docs/github-publishing/) directly. For clients that can fetch web pages, the site provides [Markdown discovery](/llms.txt), [full documentation and page text](/llms-full.txt), and a [Markdown copy of this guide](/docs/mcp.md).

## Browser editing is separate

The editor’s experimental native WebMCP integration exposes five different tools inside a compatible editor tab. Those tools work with unsaved drafts; Save and Publish remain manual. Connecting to the public endpoint above does not connect an agent to your editor.

See [Browser-assisted drafts](/docs/webmcp/) for browser support, access requirements and draft-editing tools.

Documentation

On this page