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: connect an MCP-capable agent

Integration: connect an MCP-capable agent

3 min read•Updated Sep 4, 2026

Overview

Connect an MCP-capable agent to Moxie Docs so your own automation or assistant can ask grounded questions about your repositories and use the same context Moxie uses. After setup, your MCP client can route questions to Moxie Docs’ “Ask this codebase” and reflect feedback to improve answers over time. Nothing is changed in your repositories without your review; Moxie Docs continues to only open documentation pull requests that you approve.

Before you start

  • A Moxie Docs workspace with at least one connected GitHub repository.
  • Access to Moxie Docs with permission to view Docs and Ask panels.
  • An MCP-capable client or agent you control (for example, an automation or assistant that supports MCP tools).
  • The ability to adjust settings in your MCP client.

Connect

  1. Open Moxie Docs and go to Docs.
  2. Select the repository you want your agent to use for Q&A.
  3. Open the Ask panel. This is where “Ask this codebase” lives and where feedback is captured.
  4. Review the scope shown in the Ask panel so you know which repository and branch your agent will be able to query through Moxie Docs.
  5. Open your MCP-capable client and add a new tool or data source that connects to Moxie Docs for Q&A. Use your client’s standard flow to enable a tool that can ask questions and read answers.
  6. Return to the Ask panel in Moxie Docs and submit a simple question to confirm the repository context looks right. Keep this tab open so you can compare results from your agent.

Note: If your MCP client prompts you to choose what the agent can access, select the repository you opened in the Ask panel so questions stay grounded in that codebase.

Configure

After connecting, set how the agent should use Moxie Docs:

  • Choose repository scope: Limit the agent to the repository you selected in the Ask panel for focused answers.
  • Set question style: Encourage specific questions (for example, “Where is the auth middleware registered?”) to get targeted results.
  • Enable feedback: Have the agent record thumbs up/down for each answer using the Ask panel’s feedback widget so Moxie Docs can learn from your usage.
  • Add tags on feedback: Standardize tags (for example, “correctness”, “missing context”) so trends are easy to review later.

Verify it works

  • Ask from your MCP client: Submit a question through your agent and confirm the answer matches what you see when you ask the same question in the Ask panel in Moxie Docs.
  • Check feedback capture: In the Ask panel, use the thumbs widget on the answer your agent referenced and apply a tag. Confirm your agent can reflect that outcome in its next interaction.
  • Validate repository grounding: Ask a question that only your selected repository can answer (for example, about a specific file or function name) and confirm the response references that codebase.
  • Confirm no changes occur: Ensure your agent’s use of Q&A does not create pull requests. Documentation pull requests are only opened by Moxie Docs drift detectors and require your review and merge.

Disconnect or change access

  • To change which repository the agent uses, open Docs, switch to the desired repository, and use the Ask panel there. Update your MCP client to point to that repository’s context.
  • To stop your agent from using Moxie Docs Q&A, remove the Moxie Docs tool or data source in your MCP client.
  • If you no longer want the agent’s feedback to affect learning, stop submitting thumbs up/down in the Ask panel or remove tags before saving feedback.

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 PRsThis guide helps you resolve problems when Moxie Docs cannot create or update a pull reque
GuidesTroubleshoot GitHub connection and indexingThis guide helps you fix problems connecting GitHub to Moxie Docs, granting repository acc
PreviousConfigure PR automation and detectors
Next Integration: MCP agents

On this page

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

Powered by Moxie Docs

Overview

Connect an MCP-capable agent to Moxie Docs so your own automation or assistant can ask grounded questions about your repositories and use the same context Moxie uses. After setup, your MCP client can route questions to Moxie Docs’ “Ask this codebase” and reflect feedback to improve answers over time. Nothing is changed in your repositories without your review; Moxie Docs continues to only open documentation pull requests that you approve.

Before you start

  • A Moxie Docs workspace with at least one connected GitHub repository.
  • Access to Moxie Docs with permission to view Docs and Ask panels.
  • An MCP-capable client or agent you control (for example, an automation or assistant that supports MCP tools).
  • The ability to adjust settings in your MCP client.

Connect

  1. Open Moxie Docs and go to Docs.
  2. Select the repository you want your agent to use for Q&A.
  3. Open the Ask panel. This is where “Ask this codebase” lives and where feedback is captured.
  4. Review the scope shown in the Ask panel so you know which repository and branch your agent will be able to query through Moxie Docs.
  5. Open your MCP-capable client and add a new tool or data source that connects to Moxie Docs for Q&A. Use your client’s standard flow to enable a tool that can ask questions and read answers.
  6. Return to the Ask panel in Moxie Docs and submit a simple question to confirm the repository context looks right. Keep this tab open so you can compare results from your agent.

Note: If your MCP client prompts you to choose what the agent can access, select the repository you opened in the Ask panel so questions stay grounded in that codebase.

Configure

After connecting, set how the agent should use Moxie Docs:

  • Choose repository scope: Limit the agent to the repository you selected in the Ask panel for focused answers.
  • Set question style: Encourage specific questions (for example, “Where is the auth middleware registered?”) to get targeted results.
  • Enable feedback: Have the agent record thumbs up/down for each answer using the Ask panel’s feedback widget so Moxie Docs can learn from your usage.
  • Add tags on feedback: Standardize tags (for example, “correctness”, “missing context”) so trends are easy to review later.

Verify it works

  • Ask from your MCP client: Submit a question through your agent and confirm the answer matches what you see when you ask the same question in the Ask panel in Moxie Docs.
  • Check feedback capture: In the Ask panel, use the thumbs widget on the answer your agent referenced and apply a tag. Confirm your agent can reflect that outcome in its next interaction.
  • Validate repository grounding: Ask a question that only your selected repository can answer (for example, about a specific file or function name) and confirm the response references that codebase.
  • Confirm no changes occur: Ensure your agent’s use of Q&A does not create pull requests. Documentation pull requests are only opened by Moxie Docs drift detectors and require your review and merge.

Disconnect or change access

  • To change which repository the agent uses, open Docs, switch to the desired repository, and use the Ask panel there. Update your MCP client to point to that repository’s context.
  • To stop your agent from using Moxie Docs Q&A, remove the Moxie Docs tool or data source in your MCP client.
  • If you no longer want the agent’s feedback to affect learning, stop submitting thumbs up/down in the Ask panel or remove tags before saving feedback.