From ac42080a8b1d12a590e62f272acfce9cb29f32f5 Mon Sep 17 00:00:00 2001 From: "fern-api[bot]" <115122769+fern-api[bot]@users.noreply.github.com> Date: Wed, 2 Sep 2026 21:31:03 +0000 Subject: [PATCH] =?UTF-8?q?Fix=20page-actions=20example,=20add=20subtitle/?= =?UTF-8?q?description=20table,=20add=20MCP=20"How=20=E2=80=A6?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- fern/products/docs/pages/ai/mcp-server.mdx | 6 ++++++ fern/products/docs/pages/navigation/frontmatter.mdx | 8 ++++++++ .../docs/pages/navigation/site-level-settings.mdx | 8 ++++---- 3 files changed, 18 insertions(+), 4 deletions(-) diff --git a/fern/products/docs/pages/ai/mcp-server.mdx b/fern/products/docs/pages/ai/mcp-server.mdx index f9e516711a..7e3917c774 100644 --- a/fern/products/docs/pages/ai/mcp-server.mdx +++ b/fern/products/docs/pages/ai/mcp-server.mdx @@ -9,6 +9,12 @@ This is the server your readers connect to, and it serves your content. To point Your MCP server is available at `your-documentation-site.com/_mcp/server`. For example, the MCP server for this site is at [https://buildwithfern.com/learn/_mcp/server](https://buildwithfern.com/learn/_mcp/server). +## How it works + +The MCP server exposes a single tool: a semantic search tool that lets AI clients query your documentation. The client sends a natural-language question and the server returns the most relevant passages from your docs, along with their source URLs. The search is vector-based, not keyword-based, so the server finds conceptually relevant content even when the exact words don't match. + +Each query to the MCP server counts as one Ask AI query against your plan's Ask AI usage. Monitor usage in the [Fern Dashboard](https://dashboard.buildwithfern.com/) under **Ask Fern**. + ## Connect to your MCP server For Claude Code and Cursor, [page action](/learn/docs/configuration/site-level-settings#page-actions-configuration) buttons let users connect in one click: diff --git a/fern/products/docs/pages/navigation/frontmatter.mdx b/fern/products/docs/pages/navigation/frontmatter.mdx index 11f7da40bf..f1a7d81123 100644 --- a/fern/products/docs/pages/navigation/frontmatter.mdx +++ b/fern/products/docs/pages/navigation/frontmatter.mdx @@ -101,6 +101,14 @@ navigation: `subtitle` and `description` are closely related but serve different purposes: `subtitle` is visible on the page, while `description` is metadata for search engines and social previews. When `description` is missing, Fern falls back to `subtitle` for the metadata; a missing `subtitle` simply renders nothing. +| Field | Visible on page? | Used as meta description? | Used as OG description? | +|---|---|---|---| +| `subtitle` | Yes | Fallback when `description` is absent | Fallback when `description` and `og:description` are absent | +| `description` | No | Yes | Fallback when `og:description` is absent | +| `og:description` | No | No | Yes | + +This differs from Mintlify, where `description` is the visible subtitle and `og:description` is the meta description. In Fern, `subtitle` is the visible field and `description` is the meta field. + diff --git a/fern/products/docs/pages/navigation/site-level-settings.mdx b/fern/products/docs/pages/navigation/site-level-settings.mdx index d58f9b40aa..d41010cadd 100644 --- a/fern/products/docs/pages/navigation/site-level-settings.mdx +++ b/fern/products/docs/pages/navigation/site-level-settings.mdx @@ -843,11 +843,11 @@ To hide page actions on an individual page, use the [`hide-page-actions` frontma ```yaml docs.yml page-actions: - default: cursor + default: cursor # cursor is shown as the primary action options: - copy-page: false - ask-ai: false - cursor: true + copy-page: false # disable the Copy Page button + ask-ai: false # disable the Ask AI button + cursor: true # keep Cursor enabled (independent of default) ```