Merge branch 'refresh-homepage' of https://github.com/mintlify/docs into refresh-homepage

Author: ethanpalm

.claude/CLAUDE.md

@@ -1,17 +1,6 @@
 # Mintlify documentation
 
-You are an experienced, pragmatic technical writer with robust content strategy and content design experience. You elegantly create just enough docs to solve users' needs and get them back to the product quickly.
-
-If you want an exception to ANY rule, YOU MUST STOP and get explicit permission first from the user.
-
-## Working relationship
-
-- ALWAYS ask for clarification rather than making assumptions
-- NEVER lie, guess, or make up information
-- Push back if something seems wrong or like it makes the documentation worse
-- NEVER be agreeable just to be nice - I need your honest technical judgment.
-- NEVER tell me I'm "absolutely right" or anything like that. You ARE NOT a sycophant.
-- If you are making an inference, stop and ask for confirmation or say that you need more information
+You are an experienced, pragmatic technical writer with robust content strategy and content design experience. You elegantly create just enough docs to solve users' needs and get them back to the product quickly. NEVER lie, guess, or make up information.
 
 ## Context and tool usage
 
@@ -45,7 +34,6 @@ For major documentation restructuring or complex multi-page changes:
 ## Content strategy
 - We document just enough so that users are successful. Too much content makes it hard to find what people are looking for. Too little makes it too challenging to accomplish users' goals.
 - Prioritize accuracy and usability of information
-- Make content evergreen when possible
 - Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
 - Check existing patterns for consistency
 - Start by making the smallest reasonable changes
@@ -114,23 +102,15 @@ For major documentation restructuring or complex multi-page changes:
 - Structure content in the order users need it with most commonly needed information first and most specific information last
 - Combine related information to reduce redundancy
 
-## Git workflow
-- NEVER use --no-verify when committing
-- Ask how to handle uncommitted changes before starting
-- Create a new branch when no clear branch exists for changes
-- Commit frequently throughout development
-- NEVER skip or disable pre-commit hooks
-
 ## Before submitting work
-- [ ] Preview changes locally with `mint dev`
 - [ ] Run `mint broken-links` to check internal links
 - [ ] Manually test external links don't 404
 - [ ] Run `vale $(git diff --name-only main)` to check style and spelling
 - [ ] Verify all code blocks have language tags
 - [ ] Confirm frontmatter includes title, description, keywords
 - [ ] Check formatting matches similar existing pages
 - [ ] Read changes aloud to catch awkward phrasing
-- List any uncertain areas that need extra review
+- [ ] List any uncertain areas that need extra review
 
 ## When submitting work
 
@@ -144,4 +124,3 @@ Provide a structured summary:
 - Skip frontmatter on any MDX file
 - Use absolute URLs for internal links
 - Include untested code examples
-- Make assumptions - always ask for clarification

.mintlify/AGENTS.md

@@ -0,0 +1,3 @@
+# Documentation agent instructions
+
+When you create a PR to update docs, only update English language files. Do not update any content in the `es/`, `fr/`, or `zh/` directories. A workflow handles all translations after a docs PR merges to production.

.vale/styles/config/vocabularies/Mintlify/accept.txt

@@ -41,6 +41,7 @@ Chromium
 CircleCI
 classnames?
 Clearbit
+Cloudinary
 CLI
 CNAME
 (?i)codeblocks?
@@ -63,6 +64,7 @@ desc
 Dev
 diffs?
 dir
+Discord
 discoverability
 dismissible
 Django
@@ -95,6 +97,7 @@ func
 Gantt
 GCP
 GEO
+GHES
 Git
 GitHub
 GitLab
@@ -130,6 +133,7 @@ Java
 JavaScript
 JetBrains
 JSDoc
+JSX
 KaTeX
 Kotlin
 Kubernetes
@@ -225,8 +229,10 @@ pytest
 Python
 QBRs
 quickstarts?
+RAG
 RBAC
 React
+Readybot
 redeploy(s|ed|ing)?
 Redis
 repos?
@@ -273,6 +279,7 @@ subdomains?
 subgraphs?
 subpaths?
 subschema
+subscribable
 SVGs?
 Swagger
 Swift

agent/index.mdx

@@ -48,7 +48,7 @@ Add the agent to your Slack workspace.
 <Card title="Connect Linear" horizontal icon="linear" href="/agent/linear">
 Add the agent to your Linear workspace.
 </Card>
-<Card title="Connect Notion" horizontal icon="file-lines" href="/agent/notion">
+<Card title="Connect Notion" horizontal icon="notion" href="/agent/notion">
 Give the agent access to your Notion workspace.
 </Card>
 <Card title="Customize behavior" horizontal icon="wrench" href="/agent/customize">

ai/assistant.mdx

@@ -21,15 +21,15 @@ The assistant uses agentic RAG (retrieval-augmented generation) with tool callin
 * **Generates copyable code examples** to help users implement solutions from your documentation.
 * **Supports multiple modalities** by allowing users to add text, images, and other files as context.
 
-You can view assistant usage through your dashboard to understand user behavior and documentation effectiveness. Export and analyze query data to help identify:
+View assistant usage through your dashboard to understand user behavior and documentation effectiveness. Export and analyze query data to help identify:
 
 * Frequently asked questions that might need better coverage.
 * Content gaps where users struggle to find answers.
 * Popular topics that could benefit from additional content.
 
 ### How indexing works
 
-The assistant automatically indexes your published documentation and API specifications to answer questions accurately. When you publish changes, the assistant immediately indexes new, updated, or deleted content. The assistant does not index draft branches or preview deployments.
+The assistant indexes your published documentation and API specifications to answer questions accurately. When you publish changes, the assistant immediately indexes new, updated, or deleted content. The assistant does not index draft branches or preview deployments.
 
 By default, the assistant does not index hidden pages. To include hidden pages in the assistant's index, set `seo.indexing: "all"` in your `docs.json`. See [Hidden pages](/organize/hidden-pages#search-seo-and-ai-indexing) for more information.
 
@@ -171,10 +171,6 @@ If you want to disallow overages, disable them in the **Billing Controls** secti
 
 In the Billing Controls section, set usage alerts to receive an email when you reach a certain percentage of your message allowance.
 
-## Connect apps
-
-In the connect apps section, add the assistant to your [Discord](/ai/discord) server and [Slack](/ai/slack-bot) workspace to allow users to get answers from your documentation on those platforms.
-
 ## Assistant insights
 
 Use assistant insights to understand how users interact with your documentation and identify improvement opportunities.
@@ -206,8 +202,6 @@ Structure your documentation to help the assistant provide accurate, relevant an
 
 Users have multiple ways to start a conversation with the assistant. Each method opens a chat panel on the right side of your docs. Users can ask any question and the assistant searches your documentation for an answer. If the assistant cannot retrieve relevant information, the assistant responds that it cannot answer the question.
 
-Add the assistant as a bot to your [Slack workspace](/ai/slack-bot) or [Discord server](/ai/discord) so that your community can ask questions without leaving their preferred platform.
-
 ### UI placement
 
 The assistant appears in two locations: as a button next to the search bar and as a bar at the bottom of the page.

ai/discord.mdx

@@ -4,47 +4,20 @@ description: "Set up a Discord bot that answers community questions using your d
 keywords: ["Discord", "bot", "Q&A", "customer support"]
 ---
 
-<Info>
-  Discord integrations are available on [Pro and Enterprise plans](https://mintlify.com/pricing?ref=discord) with access to the assistant.
-</Info>
+<Warning>
+  The Discord bot is deprecated.
+  
+  New Discord bot installations are not available. Existing Discord bot integrations continue to work.
+</Warning>
 
 The Discord bot supports your community with real-time answers from your documentation. The bot uses the Mintlify assistant to search your docs and provide accurate, cited responses, so it is always up-to-date.
 
 The Discord bot only works in public channels. It replies to `@` mentions or to all messages in a specific channel.
 
 Each message sent by the Discord bot counts toward your assistant message usage.
 
-## Add the Discord bot to your server
-
-<Note>
-  You must have the "Manage Server" permission in Discord to add the bot.
-</Note>
-
-1. Navigate to the [Assistant](https://dashboard.mintlify.com/products/assistant) page in your dashboard.
-1. In the Discord card, click **Configure**. This opens Discord.
-   <Frame>
-     <img src="/images/assistant/connected-apps-light.png" alt="The connected apps section of the assistant page." className="block dark:hidden" />
-     <img src="/images/assistant/connected-apps-dark.png" alt="The connected apps section of the assistant page." className="hidden dark:block" />
-   </Frame>
-1. In Discord, select the server you want to add the bot to.
-1. Authorize the bot to access your server.
-1. Mention the bot to add it to a channel. The bot's default name is `@Mintlify Bot`.
-
 ## Create an `#ask-ai` channel
 
 To help your community quickly get answers to their questions, the bot can reply to every message in a channel that you choose. By default, the bot replies to every message in channels named `#ask-ai`. Create an `#ask-ai` channel and let your community know that the bot replies to messages in that channel.
 
-If you want the bot to reply to messages in a different channel, select a channel in the Discord bot [configuration menu](https://dashboard.mintlify.com/products/assistant/settings/integrations).
-
-<Frame>
-  <img src="/images/assistant/discord-configure-light.png" alt="The Discord configuration panel in light mode." className="block dark:hidden" />
-  <img src="/images/assistant/discord-configure-dark.png" alt="The Discord configuration panel in dark mode." className="hidden dark:block" />
-</Frame>
-
 See [Starting Your First Discord Server](https://discord.com/blog/starting-your-first-discord-server) on the Discord blog for more information on creating a channel.
-
-## Manage the Discord bot
-
-After you add the Discord bot to your server, you can manage or remove the bot from the [Integrations](https://dashboard.mintlify.com/products/assistant/settings/integrations) tab in your dashboard.
-
-In the Discord bot configuration menu, customize the bot by changing its avatar or name, and choose which channel it automatically replies to all messages in.

ai/llmstxt.mdx

@@ -12,6 +12,8 @@ Mintlify automatically hosts an `llms.txt` file at the root of your project that
 
 <Note>
   If your site requires authentication, `llms.txt` and `llms-full.txt` also require authentication to view. LLMs and AI tools that cannot authenticate into your site cannot access these files. The files exclude pages that belong to [user groups](/deploy/authentication-setup#control-access-with-groups).
+
+  For more information on how authentication affects AI features, see [Feature availability](/deploy/authentication-setup#feature-availability).
 </Note>
 
 View your `llms.txt` by appending `/llms.txt` to your documentation site's URL. Mintlify also hosts the file at `/.well-known/llms.txt` for compatibility with tools that follow the `.well-known` convention.

ai/model-context-protocol.mdx

@@ -10,20 +10,29 @@ import { PreviewButton } from "/snippets/previewbutton.jsx"
 
 The Model Context Protocol (MCP) is an open protocol that creates standardized connections between AI applications and external services, like documentation. Mintlify generates an MCP server from your documentation, preparing your content for the broader AI ecosystem where any MCP client like Claude, Cursor, Goose, ChatGPT, and others can connect to your documentation.
 
-Your MCP server exposes a search tool for AI applications to query your documentation. Your users must connect your MCP server to their tools.
+Your MCP server exposes tools for AI applications to search your documentation and retrieve full page content. Your users must connect your MCP server to their tools.
 
 ### How MCP servers work
 
-When an AI application connects to your documentation MCP server, it can search your documentation directly in response to a user's prompt instead of relying on information from its training data or making a generic web search. Your MCP server provides access to all indexed content on your documentation site.
+When an AI application connects to your documentation MCP server, it can search your documentation and retrieve full page content directly in response to a user's prompt instead of relying on information from its training data or making a generic web search. Your MCP server provides access to all indexed content on your documentation site.
 
 - AI applications can proactively search your documentation while generating a response even if not explicitly asked to search your documentation for an answer.
-- AI applications determine when to use the search tool based on the context of the conversation and the relevance of your documentation.
-- Each search, also known as a tool call, happens during the generation process, so the AI application searches up-to-date information from your documentation to generate its response.
+- AI applications determine when to use the available tools based on the context of the conversation and the relevance of your documentation.
+- Each tool call happens during the generation process, so the AI application uses up-to-date information from your documentation to generate its response.
 
 <Tip>
   Some AI tools like Claude support both MCP and Skills. MCP gives the AI access to your documentation content, while Skills instruct the AI how to use that content effectively. They're complementary. MCP provides the data and Skills provide the instructions.
 </Tip>
 
+### MCP tools
+
+Your MCP server provides two tools that AI applications can use:
+
+- **Search**: Searches across your documentation to find relevant content, returning snippets with titles and links. Use this when you need to discover information or find pages matching a query.
+- **Get page**: Retrieves the full content of a specific documentation page by its path. Use this when you already know the page path, such as from search results, and need the complete content rather than a snippet.
+
+AI applications determine when to use each tool based on the context of the conversation. For example, an AI application might first search your documentation to find relevant pages, then use the get page tool to retrieve the full content of the most relevant result.
+
 ### Search parameters
 
 The MCP search tool supports optional parameters that AI applications use to control and refine search results.
@@ -35,6 +44,12 @@ The MCP search tool supports optional parameters that AI applications use to con
 
 AI applications determine when to apply these parameters based on the context of the user's query. For example, if a user asks about a specific API version, the AI application may automatically apply the appropriate filter to provide more relevant results.
 
+### Get page parameters
+
+The get page tool accepts one required parameter:
+
+- **`page`**: The page path to retrieve, such as `'api-reference/create-customer'`. Use page paths returned from search results.
+
 ### MCP compared to web search
 
 AI tools can search the web, but MCP provides distinct advantages for documentation.
@@ -96,7 +111,10 @@ To protect availability, Mintlify applies rate limits to MCP servers.
 | Scope | Limit | Description |
 | :---- | :---- | :---------- |
 | Per user (IP address) | 5,000 requests per hour | Limits how frequently a single user can query your MCP server configuration. |
-| Per documentation site (domain) | 10,000 requests per hour | Limits total searches across all users of your MCP server. |
+| Search per documentation site (domain) | 10,000 requests per hour | Limits total search tool calls across all users of your MCP server. |
+| Get page per documentation site (domain) | 10,000 requests per hour | Limits total get page tool calls across all users of your MCP server. |
+| Authenticated search per documentation site (domain) | 5,000 requests per hour | Limits total authenticated search tool calls across all users of your MCP server. |
+| Authenticated get page per documentation site (domain) | 5,000 requests per hour | Limits total authenticated get page tool calls across all users of your MCP server. |
 
 ## Content filtering and indexing
 

ai/slack-bot.mdx

@@ -4,9 +4,11 @@ description: "Set up a Slack bot that answers team questions using your document
 keywords: ["bot", "workspace", "Q&A", "Slack", "app"]
 ---
 
-<Info>
-  The Slack app is available for [Pro and Custom plans](https://mintlify.com/pricing?ref=slack-app) with access to the assistant.
-</Info>
+<Warning>
+  The Slack bot is deprecated.
+
+  New Slack bot installations are not available. Existing Slack bot integrations continue to work.
+</Warning>
 
 The Slack app adds a bot to your workspace that supports your community with real-time answers. The bot uses the Mintlify assistant to search your docs and provide accurate, cited responses, so it is always up-to-date.
 
@@ -16,36 +18,6 @@ The bot responds to `@` mentions or to all messages in a specific channel that y
 
 Each message sent by the bot counts toward your assistant message usage.
 
-## Set up the Slack app
-
-<Note>
-  You can only install the Slack app once per workspace. If you have multiple Mintlify deployments, you can only connect one deployment at a time to a workspace. You must disconnect the app from one deployment before connecting it to another.
-</Note>
-
-If your Slack Workspace Owner requires admin approval to install apps, ask them to approve the Mintlify Slack app before you add it.
-
-1. Navigate to the [Assistant](https://dashboard.mintlify.com/products/assistant) page in your dashboard.
-1. In the Slack card, click **Configure**. This opens Slack.
-    <Frame>
-      <img src="/images/assistant/connected-apps-light.png" alt="The connected apps section of the assistant page." className="block dark:hidden" />
-      <img src="/images/assistant/connected-apps-dark.png" alt="The connected apps section of the assistant page." className="hidden dark:block" />
-    </Frame>
-1. Follow the Slack prompts to add the app to your workspace.
-1. Mention the bot to add it to a channel. The bot's default name is `@mintlify-assistant`.
-
 ## Create an `#ask-ai` channel
 
 To help your users quickly get answers to their questions, the bot can reply to every message in a channel that you choose. By default, the bot replies to every message in channels named `#ask-ai`. Create an `#ask-ai` channel and let your users know that the bot replies to messages in that channel. See [Create a channel](https://slack.com/help/articles/201402297-Create-a-channel) in the Slack Help Center for more information.
-
-If you want the bot to reply to messages in a different channel, select a channel in the Slack bot [configuration menu](https://dashboard.mintlify.com/products/assistant/settings/integrations).
-
-<Frame>
-  <img src="/images/assistant/slack-configure-light.png" alt="The Slack configuration panel in light mode." className="block dark:hidden" />
-  <img src="/images/assistant/slack-configure-dark.png" alt="The Slack configuration panel in dark mode." className="hidden dark:block" />
-</Frame>
-
-## Manage the Slack app
-
-After you add the app to your workspace, you can manage or remove the app from the [Integrations](https://dashboard.mintlify.com/products/assistant/settings/integrations) tab.
-
-In the Slack bot configuration menu, customize the bot by changing its avatar or name, and choose which channel it automatically replies to all messages in.