# Connect an AI assistant to the Udibo docs

Udibo serves its published documentation to AI assistants over the Model Context
Protocol (MCP). An assistant that connects can search the docs and read a page
as markdown while it answers your question or writes your integration, instead
of working from what it remembers. The endpoint is read-only. It needs no Udibo
account and no key.

## Endpoint

| Setting   | Value                                                                    |
| --------- | ------------------------------------------------------------------------ |
| URL       | `https://mcp.udibo.com/docs`                                             |
| Transport | Streamable HTTP; every request is a `POST`                               |
| Sign-in   | None. Send no credential                                                 |
| Server card | `https://mcp.udibo.com/docs/server-card`, a public JSON description of the endpoint |

The server keeps no session, so a client sends no session id. Each answer is one
JSON response.

## Connect a client

Any MCP client that supports remote servers over Streamable HTTP connects with
the URL and transport above and no authentication. If your client asks for a
name, use `udibo-docs`. After connecting, the client lists two tools, `search`
and `fetch`.

### Claude Code

Claude Code adds a remote server with `claude mcp add --transport http`:

```sh
claude mcp add --transport http udibo-docs https://mcp.udibo.com/docs
```

Check the connection with `claude mcp list` or `/mcp`. Claude Code's
[MCP documentation](https://code.claude.com/docs/en/mcp) covers scopes and
managing servers.

### Claude on the web and desktop

Claude adds a server it does not list in its directory as a custom connector by
URL. Use `https://mcp.udibo.com/docs` as the server URL. The endpoint needs no
sign-in, so choose the **No sign-in** authentication option. Anthropic's page
[Add a connector that isn't in the directory](https://claude.com/docs/connectors/custom/add-unlisted.md)
has the current steps, plan requirements, and the authentication options. On a
Team or Enterprise plan an organization Owner adds the connector.

### Other assistants

This page has no steps for other assistants. Use their own documentation for
adding a remote MCP server, with the URL and transport above.

## What the tools do

Both tools only read. Neither changes anything at Udibo, and both reach only
Udibo's published documentation for Udibo Identity and the `@udibo/oauth2`
package. Neither reads an internal page, a draft, or any address outside the
published set.

| Tool     | Input                                                                                          | Returns                                                                                              |
| -------- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| `search` | `query`: keywords, 1 to 100 characters                                                         | At most 10 pages, each with `id`, `title`, public `url`, and an `excerpt` of the page summary of at most 300 characters |
| `fetch`  | `id`: a search result's `id`, a docs path such as `/docs/identity/get-started`, or the page's `https://www.udibo.com` URL, up to 512 characters | The page's `id`, `title`, `url`, and `text`, its published markdown                                  |

`search` matches against page titles, summaries, and addresses, not the full
text of a page. Every word in the query must appear, so a short query such as
`passkeys` or `refresh token` works better than a sentence. A query that
matches nothing returns an empty list.

`fetch` returns the same markdown as a page's `.md` address. An address that
does not name a published page gives a tool error, "No published documentation
page has that address. Use search to find one." The tool does not fetch other
websites.

## Limits and refusals

- **Rate limit.** An address may make 120 requests a minute to the endpoint.
  Clients behind one shared address share that budget. Past it, the endpoint
  answers `429` with a `Retry-After` header in seconds, and a JSON-RPC error
  whose message is "Too Many Requests: slow down and retry later." Wait that
  long and retry.
- **Browser origins.** A request that carries an `Origin` header other than
  `https://mcp.udibo.com` gets `403` ("Forbidden: this Origin may not call the
  endpoint."), and no response carries a CORS grant. Assistants' servers and
  desktop clients send no `Origin` and are served; a web page's script cannot
  call the endpoint. The server card is the exception: any origin may read it.
- **Methods.** Any method other than `POST` gets `405` with `Allow: POST`.
- **Request size and shape.** A request body over 64 KiB gets `413`. A batch of
  several JSON-RPC messages in one request is refused with `400`; send one
  message per request.
- **Protocol versions.** The endpoint serves MCP revisions `2025-11-25`,
  `2025-06-18`, `2025-03-26`, `2024-11-05`, and `2024-10-07`. A client that asks
  to initialize at a revision the endpoint does not serve is answered at
  `2025-11-25`; a request that names an unserved revision in its
  `MCP-Protocol-Version` header gets `400`.
- **Unexpected failures.** An internal error answers `500`, and a tool that
  fails unexpectedly returns an error result ("The tool failed."), each with a
  reference id in the message. Quote that id if you ask Udibo about the failure.

## What a query sends to Udibo

A call sends the search words or page address you or your assistant chose, in
the body of a request to `mcp.udibo.com`. The endpoint reads no cookie and
resolves no account. Udibo uses the search words and page address only to
answer the request and does not keep them, as its
[Privacy Policy](https://www.udibo.com/privacy) says. The policy also describes
what Udibo and its providers process when systems are visited and secured,
including network addresses, timestamps, requested pages, responses, and
security events, and who receives it. That policy is the whole statement; this
page promises nothing beyond it. What your assistant's vendor does with the
conversation that surrounds the call is governed by the vendor's own terms.

## Keep reading

- [Build with an agent](https://www.udibo.com/docs/identity/agents) gives a
  coding agent the integration brief and acceptance checks.
- [All docs as an agent index](https://www.udibo.com/llms.txt) lists every
  published page for an agent that reads over plain HTTP.

_Last verified 2026-11-11._