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

# MCP servers

> The lab's content and tools, exposed for AI agents.

The lab exposes its documentation as read-only MCP servers, so AI agents can search and cite the source material directly instead of guessing.

## Lab hub — mcp.uzenlabs.com

A unified endpoint aggregating the docs manifests published by the lab's properties:

```text theme={null}
https://mcp.uzenlabs.com
```

Streamable HTTP, no authentication, read-only. Send MCP requests to the root path; sources are refreshed automatically as the underlying sites redeploy.

```json theme={null}
{
  "mcpServers": {
    "uzenlabs": {
      "url": "https://mcp.uzenlabs.com"
    }
  }
}
```

## Onchain Diary

Full content library — research articles, the glossary, and hub pages, in English and Chinese:

```text theme={null}
https://theonchaindiary.com/api/mcp
```

Same protocol: streamable HTTP, no auth, read-only. Tools include content search, article reading, and glossary lookup.

## Tool-bundled servers

Two projects ship their own MCP servers as part of the product:

* **ZensInk** — the CLI includes an MCP server exposing every tool: `python3 -m zens_ink.mcp`. See [ZensInk](/products/zensink).
* **Margin (LiteInk theme)** — the theme bundles a theme-aware MCP server with component, content-schema, and config tools, plus `/.well-known/mcp.json` for auto-discovery. See [github.com/Liteink/margin](https://github.com/Liteink/margin).

## House rules

All lab MCP servers are read-only. If you need write access to something, that's a conversation, not an endpoint.