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

# Frontic Docs

The **Frontic Docs** MCP server is a read-only endpoint that exposes the Frontic documentation to any MCP-compatible AI agent. Connect it alongside [Frontic Tools](/reference/mcp/frontic-tools) and your editor's agent can answer "how does X work?" questions by querying the docs directly — no leaving the editor, no tab-switching to read.

The docs MCP needs no authentication. It's a public, read-only resource — same one this site is built from.

## What it's good for

<CardGroup cols={2}>
  <Card title="Answering how-to questions inline" icon="circle-question">
    Your agent looks up the right documentation page when you ask
    something like "how do I configure a domain?" — pulling the
    answer into the conversation rather than guessing.
  </Card>

  <Card title="Grounding generated code" icon="anchor">
    When the agent writes against the Frontic SDK or API, it can
    cross-reference the docs to make sure it's using the right
    method shape, the right parameters, the right defaults.
  </Card>

  <Card title="Onboarding teammates" icon="user-plus">
    A new dev's editor agent can answer Frontic-specific questions
    immediately, instead of asking them to dig through the docs site
    while learning the codebase.
  </Card>

  <Card title="Cross-checking against changes" icon="arrows-left-right">
    The docs MCP always serves the current docs site, so an agent's
    answer about a feature is as fresh as the latest documentation
    publish.
  </Card>
</CardGroup>

## Setup

The fastest path is the CLI — pick your package manager:

<CodeGroup>
  ```bash frontic theme={"theme":"css-variables"}
  frontic mcp init --client cursor
  ```

  ```bash pnpm theme={"theme":"css-variables"}
  pnpm dlx @frontic/cli@latest mcp init --client cursor
  ```

  ```bash npm theme={"theme":"css-variables"}
  npx @frontic/cli@latest mcp init --client cursor
  ```

  ```bash yarn theme={"theme":"css-variables"}
  yarn dlx @frontic/cli@latest mcp init --client cursor
  ```

  ```bash bun theme={"theme":"css-variables"}
  bunx @frontic/cli@latest mcp init --client cursor
  ```
</CodeGroup>

Swap `cursor` for `claude`, `windsurf`, `vscode`, or `codex`. The CLI prompts you to pick what to install — choose **Docs only** (or **Tools & Docs** if you also want [Frontic Tools](/reference/mcp/frontic-tools)). See the [Frontic CLI reference](/reference/frontic-cli#frontic-mcp-init) for full options.

If you'd rather edit the config yourself, drop this entry into your client's MCP config file:

```json theme={"theme":"css-variables"}
{
  "mcpServers": {
    "frontic-docs": {
      "type": "http",
      "url": "https://docs.frontic.com/mcp"
    }
  }
}
```

<Info>
  No authentication is required — the Frontic Docs MCP is public and read-only.
</Info>

### Client-specific configuration

<Accordion title="Claude Code">
  Add to `.mcp.json` at your project root — Claude Code reads project MCP config from this file:

  ```json theme={"theme":"css-variables"}
  {
    "mcpServers": {
      "frontic-docs": {
        "type": "http",
        "url": "https://docs.frontic.com/mcp"
      }
    }
  }
  ```
</Accordion>

<Accordion title="Claude Desktop">
  Edit the Claude Desktop config file:

  * **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
  * **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`

  ```json theme={"theme":"css-variables"}
  {
    "mcpServers": {
      "frontic-docs": {
        "type": "http",
        "url": "https://docs.frontic.com/mcp"
      }
    }
  }
  ```
</Accordion>

<Accordion title="Cursor">
  Add to `.cursor/mcp.json` in your project root, or Cursor's global settings:

  ```json theme={"theme":"css-variables"}
  {
    "mcpServers": {
      "frontic-docs": {
        "type": "http",
        "url": "https://docs.frontic.com/mcp"
      }
    }
  }
  ```
</Accordion>

## Example prompts

Once connected, ask questions you'd otherwise look up by hand:

<Prompt description="Ask Frontic a concept question without leaving the editor">How does request context get resolved from a domain in Frontic?</Prompt>

<Prompt description="Look up an SDK response shape from the docs">What does the response shape of a Page look like in the Client SDK?</Prompt>

<Prompt description="Get a step-by-step answer for how to set up a feature">What are the steps to add a new locale to a Frontic project?</Prompt>

<Prompt description="Have the docs MCP pull a reference catalogue for you">List the Value Composer operations available in the Text category.</Prompt>

The agent calls the docs MCP, retrieves the relevant section, and answers from it — usually citing the page so you can follow up if you need more depth.

## Pairing with Frontic Tools

The two MCP servers compose naturally: Frontic Tools acts on your project, Frontic Docs explains the platform. With both connected, an agent can read the docs to learn what it should be doing, then use the project tools to do it. That's the recommended setup for any IDE-side Frontic workflow — install both via `frontic mcp init` and pick **Tools & Docs** at the prompt.

## Related

<CardGroup cols={2}>
  <Card title="Frontic Tools" icon="microchip-ai" href="/reference/mcp/frontic-tools">
    The MCP server that acts on your Frontic project — full tool catalogue.
  </Card>

  <Card title="Frontic CLI" icon="terminal" href="/reference/frontic-cli#frontic-mcp-init">
    The `frontic mcp init` command that wires both MCP servers into your client.
  </Card>

  <Card title="MCP Tools" icon="microchip-ai" href="/ide/mcp-tools">
    Editor-facing walkthrough for setting up Frontic MCP in Claude Code, Cursor, and friends.
  </Card>
</CardGroup>