# Documentation through MCP

Use the same published Markdown through the website or a read-only MCP server.

## Connect a client

Select a remote HTTP MCP connection in your client.
Enter this endpoint:

```text
https://rom.cybernomad.it/mcp
```

The endpoint uses Streamable HTTP. It accepts POST requests and returns JSON responses. It does not require a login.
Clients must send both `application/json` and `text/event-stream` in the Accept header, as required by the transport.
A normal browser GET returns 405. This is not a documentation loading failure.

For clients that accept JSON server configuration, use:

```json
{
  "mcpServers": {
    "rom-docs": {
      "url": "https://rom.cybernomad.it/mcp"
    }
  }
}
```

Configuration keys vary between clients. Use the client's remote HTTP connection option if it does not accept this format.

## Read the documentation

| Tool | Input | Result |
| --- | --- | --- |
| `list_docs` | Optional `group`, `offset` and `limit` | Document metadata, total count and next offset |
| `search_docs` | `query` and optional `limit` | Documents that contain every query word |
| `read_doc` | A catalog `slug` | Exact published Markdown and source metadata |

Start with `search_docs` when you do not know the slug.
Use `read_doc` to obtain the full contract before designing an integration.
Continue `list_docs` pagination until `nextOffset` is null.

Each document is also an MCP resource:

```text
rom-docs://documentation/getting-started
rom-docs://documentation/component-controls-input
rom-docs://documentation/extras-overview
```

Resource reads return the same Markdown as the website download.
Unknown document slugs produce an explicit tool error.
Search returns at most 20 results. Listing returns at most 100 documents per request.

## Source and release limits

The catalog includes ROM 0.1.0 candidate documentation, ROM UI 0.1.0-alpha.7 components and the captured ROM Extras source.
Read release status before choosing a production integration.
A successful document read does not establish provider conformance.

The server exposes public documentation only. It does not execute actions or change Resources.

## Planned architecture tools

A website OpenSpec proposal records future architecture assistance.
The proposed model separates entities, relationships, Resource fields, actions, events, authorization and adapter boundaries.
These architecture tools are not available in the current MCP server.