Docs, for Moxie Docs
DocumentationGuides
  • Account and email preferences
  • Activate and index a repo
  • Changelog from PRs
  • Changelog timeline and overrides
  • Delete your account and feedback
  • Docs Home and collections
  • Drift detection and PR automation
  • Friday Recap and weekly updates
  • Give feedback on answers
  • Manage subscription
  • Publish knowledge base
  • Review drift cards and open focused doc PRs
  • Set up your public knowledgebase
  • Set your collection preferences
  • Tune repository automation settings
  • Use code previews and search helpers
  • Use Friday Recap and Cleanup
  • Workspace onboarding and invitations
  • Admin blog via SnowSEO webhook
  • Billing, trial, or access issues
  • Configure PR automation and detectors
  • Integration: connect an MCP-capable agent
  • Integration: MCP agents
  • Opportunity cards seem noisy or wrong
  • Q&A answers seem wrong or outdated
  • Share changelog to Slack
  • Stripe billing setup and syncing
  • Troubleshoot GitHub App and repository access
  • Troubleshoot GitHub connection and indexing
  • Troubleshoot GitHub PRs
  • Troubleshoot indexing
HomeGuidesIntegration: MCP agents

Integration: MCP agents

3 min read•Updated Jul 23, 2026

Overview

This integration connects a Model Context Protocol (MCP)–capable agent to your Moxie Docs knowledgebase. After setup, your agent can read repository conventions captured by Moxie, search across generated documentation, and assist with drift review and preparing updates that you can turn into PRs in your GitHub repo through the Moxie dashboard.

Before you start

  • A Moxie Docs workspace connected to your GitHub repository.
  • Access to the Moxie dashboard for your workspace.
  • An MCP-capable agent that can read from external knowledge sources you provide (for example, by following links you share).
  • Permission to share read-only links or content snippets from your Moxie Docs knowledgebase with your agent.

Connect

  1. Open the Moxie dashboard and go to your Docs home. You should see the search bar and your collections.
  2. Locate the repository conventions and documentation you want your MCP agent to use. You can browse collections or use the search bar on Docs Home and collection views.
  3. Share the relevant page links or content with your MCP agent. Provide the agent with the URLs to the Moxie-generated pages or paste the content you want it to reference. If your agent supports following links, give it the page links directly; otherwise, supply the text content.
  4. Explain to your agent how to use the knowledgebase: that it can query the same documentation you see in Moxie and that drift findings indicate where docs may need updates. Point it to the pages that contain your conventions and any drift review summaries you plan to act on.

Note: Moxie Docs is the system of record. Your MCP agent reads what you share; creating and merging PRs still happens in Moxie and GitHub.

Configure

  • Scope: Share only the pages or collections your agent needs (for example, coding conventions, API usage guides, runbooks).
  • Search behavior: Use Moxie’s search bar in the dashboard to find high-signal pages. Provide those links or excerpts to your agent for context.
  • Drift review: Include links or excerpts that show drift findings (type and severity) so your agent can help you draft updates.
  • Feedback loop: When the agent suggests changes, plan to preview and create PRs through the Moxie dashboard so changes land in your GitHub repo.

Verify it works

  • Ask your agent a question that is answered in a Moxie page you shared. Confirm it cites or reflects the conventions from that page.
  • Provide a link to a page with drift findings and ask the agent to summarize the items by type and severity. Check that its summary matches what you see in Moxie.
  • Have the agent propose doc updates based on a drift finding. Compare its draft to the source page in Moxie before creating a PR in the dashboard.
  • Use the Moxie search bar to find a specific topic, share that page with the agent, and confirm it updates its answer using the new context.

Disconnect or change access

  • To revoke access, stop sharing links or content with the agent and remove any stored context in the agent’s memory or project history.
  • To change scope, provide updated page links or replace previously shared excerpts with the new, correct pages from Moxie.
  • PR creation and review remain in Moxie and GitHub. If you decide not to use the agent’s suggestions, proceed with your usual review in the Moxie dashboard and dismiss or mute drift items as needed.

Was this page helpful?

Let us know if you found what you were looking for.

Related articles

GuidesTroubleshoot indexingThis guide helps you fix common issues that stop documentation from generating in Moxie Do
GuidesTroubleshoot GitHub connection and indexingThis guide helps you fix problems connecting GitHub to Moxie Docs, granting repository acc
GuidesTroubleshoot GitHub App and repository accessUse this guide to fix problems that stop Moxie Docs from connecting to GitHub, syncing rep
PreviousIntegration: connect an MCP-capable agent
Next Opportunity cards seem noisy or wrong

On this page

  • Overview
  • Before you start
  • Connect
  • Configure
  • Verify it works
  • Disconnect or change access
Changelogllms.txt

Powered by Moxie Docs

Overview

This integration connects a Model Context Protocol (MCP)–capable agent to your Moxie Docs knowledgebase. After setup, your agent can read repository conventions captured by Moxie, search across generated documentation, and assist with drift review and preparing updates that you can turn into PRs in your GitHub repo through the Moxie dashboard.

Before you start

  • A Moxie Docs workspace connected to your GitHub repository.
  • Access to the Moxie dashboard for your workspace.
  • An MCP-capable agent that can read from external knowledge sources you provide (for example, by following links you share).
  • Permission to share read-only links or content snippets from your Moxie Docs knowledgebase with your agent.

Connect

  1. Open the Moxie dashboard and go to your Docs home. You should see the search bar and your collections.
  2. Locate the repository conventions and documentation you want your MCP agent to use. You can browse collections or use the search bar on Docs Home and collection views.
  3. Share the relevant page links or content with your MCP agent. Provide the agent with the URLs to the Moxie-generated pages or paste the content you want it to reference. If your agent supports following links, give it the page links directly; otherwise, supply the text content.
  4. Explain to your agent how to use the knowledgebase: that it can query the same documentation you see in Moxie and that drift findings indicate where docs may need updates. Point it to the pages that contain your conventions and any drift review summaries you plan to act on.

Note: Moxie Docs is the system of record. Your MCP agent reads what you share; creating and merging PRs still happens in Moxie and GitHub.

Configure

  • Scope: Share only the pages or collections your agent needs (for example, coding conventions, API usage guides, runbooks).
  • Search behavior: Use Moxie’s search bar in the dashboard to find high-signal pages. Provide those links or excerpts to your agent for context.
  • Drift review: Include links or excerpts that show drift findings (type and severity) so your agent can help you draft updates.
  • Feedback loop: When the agent suggests changes, plan to preview and create PRs through the Moxie dashboard so changes land in your GitHub repo.

Verify it works

  • Ask your agent a question that is answered in a Moxie page you shared. Confirm it cites or reflects the conventions from that page.
  • Provide a link to a page with drift findings and ask the agent to summarize the items by type and severity. Check that its summary matches what you see in Moxie.
  • Have the agent propose doc updates based on a drift finding. Compare its draft to the source page in Moxie before creating a PR in the dashboard.
  • Use the Moxie search bar to find a specific topic, share that page with the agent, and confirm it updates its answer using the new context.

Disconnect or change access

  • To revoke access, stop sharing links or content with the agent and remove any stored context in the agent’s memory or project history.
  • To change scope, provide updated page links or replace previously shared excerpts with the new, correct pages from Moxie.
  • PR creation and review remain in Moxie and GitHub. If you decide not to use the agent’s suggestions, proceed with your usual review in the Moxie dashboard and dismiss or mute drift items as needed.