# Documentation discovery

The Veyl package includes its SDK documentation and can expose those exact files as read-only MCP resources:

```bash
veyl docs mcp
```

The process reads JSON-RPC from stdin and writes responses to stdout. It advertises only the MCP `resources` capability. It cannot load a Veyl profile, authenticate, unlock a vault, read a chat, inspect a wallet, or invoke an SDK operation.

## Host setup

Codex:

```bash
codex mcp add veyl-docs -- npx -y @glyphteck/veyl docs mcp
```

Claude Code:

```bash
claude mcp add --scope user --transport stdio veyl-docs -- npx -y @glyphteck/veyl docs mcp
```

Generic local configuration:

```json
{
  "command": "npx",
  "args": ["-y", "@glyphteck/veyl", "docs", "mcp"]
}
```

## Resources

Use `resources/list` to discover the installed documentation and `resources/read` with one returned `veyl://docs/...` URI to read a page. The resource server uses a fixed allowlist over files shipped in the package; it does not accept filesystem paths or fetch remote content.

The installed documentation always matches the installed SDK version. Agents with normal filesystem or web access may instead read the package Markdown directly or use the hosted documentation index. MCP is an optional discovery transport, not a second API.