With one command your coding agent can list Starlight packages, plan an install, search Atlas, and query verified documentation. Both endpoints are public and read-only: they need no account and cannot change anything outside their own reply.

## Before you begin [#before-you-begin]

- One of the coding agents below, installed and signed in.
- Network access to `starlightintelligence.ai` and `docs.starlightintelligence.ai`.

## Add the Starlight MCP endpoint [#add-the-starlight-mcp-endpoint]

Pick your agent below. Each command registers a server called `starlight` that speaks Streamable HTTP against `https://starlightintelligence.ai/mcp`.

<HarnessTabs
  items={[
    {
      label: 'Claude Code',
      code: 'claude mcp add --transport http starlight https://starlightintelligence.ai/mcp',
      body: 'Adds the server for the current project. Use --scope user to make it available everywhere, or --scope project to share it through .mcp.json. Project-scoped servers wait for your approval on next launch.',
    },
    {
      label: 'Codex',
      code: 'codex mcp add starlight --url https://starlightintelligence.ai/mcp',
      body: 'Writes the server to ~/.codex/config.toml. codex mcp list shows it as enabled; the Auth column reads Unsupported because this endpoint needs no sign-in.',
    },
    {
      label: 'Gemini CLI',
      code: 'gemini mcp add --transport http starlight https://starlightintelligence.ai/mcp',
      body: 'Writes .gemini/settings.json in the current folder. gemini mcp list reports Connected.',
    },
    {
      label: 'Grok',
      code: 'grok mcp add starlight https://starlightintelligence.ai/mcp',
      body: 'Grok selects HTTP transport automatically when given an https:// URL. Run grok mcp doctor to verify the connection.',
    },
  ]}
/>

> **What was tested:** On 20 October 2026 these commands were executed against the live endpoint in clean configuration folders: Gemini CLI `0.60.0` reported `Connected`, Codex `0.163.0` listed the server as enabled, and Claude Code `2.1.303` added it and held project scope for approval as documented. The Grok command was verified against `grok mcp add --help` in Grok `1.0.62`.

## Add the Docs MCP endpoint (`/api/mcp`) [#add-the-docs-mcp-endpoint-apimcp]

To give your agent direct search and citation tools (`list_docs`, `search_docs`, `get_doc`) across all five brands on this documentation platform:

<HarnessTabs
  items={[
    {
      label: 'Claude Code',
      code: 'claude mcp add --transport http starlight-docs https://docs.starlightintelligence.ai/api/mcp',
      body: 'Exposes list_docs, search_docs, and get_doc with frontmatter provenance citations.',
    },
    {
      label: 'Codex',
      code: 'codex mcp add starlight-docs --url https://docs.starlightintelligence.ai/api/mcp',
      body: 'Registers the estate docs MCP server in ~/.codex/config.toml.',
    },
    {
      label: 'Gemini CLI',
      code: 'gemini mcp add --transport http starlight-docs https://docs.starlightintelligence.ai/api/mcp',
      body: 'Adds the estate docs MCP server to .gemini/settings.json.',
    },
    {
      label: 'Grok',
      code: 'grok mcp add starlight-docs https://docs.starlightintelligence.ai/api/mcp',
      body: 'Registers the HTTP MCP server for verified documentation lookup.',
    },
  ]}
/>

## Try your first tool call [#try-your-first-tool-call]

Start your agent and ask it a question that uses the tools:

```text
List the Starlight department packages, then compile an install plan for growth-studio on Codex.
```

You will see it call `list_department_packages` and `compile_install_plan`. Install plans exist for `codex`, `claude`, `grok`, `openclaw`, `hermes`, `antigravity`, `mcp`, and `a2a`.

## No agent handy? Use curl [#no-agent-handy-use-curl]

```bash
curl https://starlightintelligence.ai/mcp \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

Or query this documentation server directly:

```bash
curl https://docs.starlightintelligence.ai/api/mcp \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_docs","arguments":{"query":"mcp","brand":"starlight"}}}'
```

## Operational limits [#operational-limits]

- `POST` executes JSON-RPC tool calls; `GET /api/mcp` on the docs server returns human-readable discovery metadata.
- Request bodies up to 64 KiB, rate-limited to 60 requests per minute per address.
- Supports protocol revision `2026-07-28` as well as legacy revisions (`2025-11-25`, `2025-06-18`, `2025-03-26`). See the [MCP tools reference](/starlight/mcp-tools) for full schemas.