Moxie Docs MCP Server

by jackalope-dev Your server? Claim it

answering

Moxie Docs is answering right now. Last checked 8 min ago. It exposes 12 tools. Last commit 24 Aug 2026.

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1089 ms

Response time

average over 24h

Stars

last commit 24 Aug 2026

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command src/cli/browser.ts:29

    const child = spawn(command, args, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add moxie-docs --transport http https://moxiedocs.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "moxie-docs": {
      "url": "https://moxiedocs.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.moxie-docs]
url = "https://moxiedocs.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "moxie-docs": {
      "url": "https://moxiedocs.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "moxie-docs": {
      "url": "https://moxiedocs.com/api/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

moxie

moxie.get_ai_context

Get the compact briefing an agent should read before editing this repository: index status, verified commands, agent tips, top conventions, open documentation gaps, and queued documentation opportunities. Read-only; no side effects. Returns a single Markdown document. Call this first at the start of a task; once you know which files you'll change, follow up with get_doc_impact for path-scoped guidance.

moxie.get_api_context

Given file paths an agent is about to touch, return structured context for any API endpoints they map to: method, path, request/response schema, and known consumers/features. Read-only; no side effects. Call this before editing API route or schema code, alongside get_doc_impact.

moxie.get_conventions

Get the coding conventions Moxie inferred for the repository. Read-only; no side effects. Returns a Markdown list grouped by category (e.g. testing, structure, docs, review); each convention has a title, summary, confidence score, agent guidance, and the source file paths that evidence it. Use this for the general rules to follow; when you already know the files you're about to edit, prefer moxie.get_doc_impact for conventions scoped to those paths.

moxie.get_doc_gaps

List the unresolved documentation gaps Moxie found - areas of the codebase that lack docs. Read-only; no side effects. Returns a Markdown list, each gap with a title, severity, summary, and suggested file paths. This is gaps only; for the full prioritized work queue that also includes drift repairs and PR-template work, use get_documentation_opportunities, and to scope gaps to files you're about to edit use get_doc_impact.

moxie.get_doc_impact

Given the file paths an agent is about to change (and optionally a subset being deleted), return the conventions, documentation gaps, and existing/related docs whose evidence overlaps those paths, plus a net-new/undocumented analysis and any removal candidates. Read-only; no side effects. Returns a Markdown report. Call this BEFORE writing code so doc updates land in the same PR; then use propose_doc_update to write a doc, or propose_doc_removal for an orphaned one.

moxie.get_documentation_opportunities

List the actionable documentation updates Moxie recommends as a prioritized queue: missing docs, drift repairs, and PR-template work. Read-only; no side effects. Returns a Markdown list, each opportunity with a title, kind (documentation_gap | documentation_drift | pr_template), severity, summary, suggested action, estimated files changed, and source paths. Use this to pick the next doc task; it is the superset of get_doc_gaps (which lists gaps only).

moxie.get_documentation_patterns

Get Moxie's summary of how THIS repository organizes and maintains documentation - where docs live relative to code and how they are kept current. Read-only; no side effects. Returns a Markdown list of pattern entries, each with a title, explanation, and source citations. Use this to decide WHERE a new doc should go before calling propose_doc_update; for the list of WHICH docs need work, use get_documentation_opportunities instead.

moxie.list_docs

List the repository's generated documentation as a browsable table of contents - every doc page, not a query-filtered subset. Read-only; no side effects. Returns Markdown grouped by section, each entry with its title, slug, repository path, and source paths, plus the total count and a pagination cursor so you can tell whether more pages remain (no silent truncation). Use this to see what docs already exist before adding one (so you don't duplicate) or to find the slug to pass to propose_doc_update; when you are hunting for a specific topic, search_docs is more direct.

moxie.propose_doc_removal

Propose deleting a Moxie-tracked documentation file that your change makes irrelevant, as part of YOUR current change. Moxie validates the path and returns it for you to delete in your working branch; Moxie itself does not delete files or open a PR - the deletion happens in your branch, so it lands in the SAME PR as the code. Returns the resolved path to delete. Provide either slug or targetPath.

moxie.propose_doc_update

Propose a documentation file to add or update as part of YOUR current change. Records a new proposal each call (not idempotent) and does NOT modify your repository or open a PR - Moxie resolves the target path and returns the path + Markdown for YOU to write into your working branch, so the docs land in the SAME PR as the code. Returns the resolved target path and the content to write. Provide either targetPath or baseSlug.

moxie.review_change

Self-review a change you are about to commit BEFORE opening the PR. Pass the proposed new state of each changed file (and any deleted paths); Moxie returns a severity-ranked list of violations to fix: convention breaches, docs your change makes factually false, net-new API/surface added without docs, and doc references broken by deletions. Read-only; no side effects and no writes. Returns a Markdown verdict (clean | warnings | must-fix) with each finding's location, fix, and - for doc issues - the slug to pass to propose_doc_update. Call this as the final step of the edit flow, then fix findings and re-run.

moxie.search_docs

Keyword and semantic search across the connected repository's generated docs, conventions, documentation gaps, AI-context notes, and indexed code. Read-only; no side effects. Returns ranked matches in Markdown grouped into Documentation and Code sections, each with a title, snippet, and source paths. Use for open-ended lookups when you don't know which category holds the answer; when you do, the specific getters (get_conventions, get_doc_gaps, get_documentation_opportunities) are more direct. Omitting query returns recent context instead.

Endpoints

URL	Transport	State	Latency	Checked
https://moxiedocs.com/api/mcp	streamable-http	answering	1274 ms	8 min ago

Alternatives to Moxie Docs

same job, measured the same way

Agent Memory MCP

by ipiton

Memory, docs, and repo context layer for engineering agents.

local only

Mne Docs

by weiyongxu

MCP server for MNE-Python documentation, source code, GitHub issues, and forum

115 installs/wk local only

Ctx

by vanshulgoyal101

Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.

6 tools answering

Gread

by nitrorcr

An MCP server that gives your AI access to the source code and docs of all public github repos

5 tools answering

RepoFold

by repofold

A cited wiki of your GitHub repo: search, read pages, find symbols and ask, with line citations.

answering

Skills Anywhere

by noteflowai

Every Agent Skill installed for any coding agent, plus GitHub skill repos, as MCP tools/resources.

1 751 installs/wk local only

CodeWiki MCP — AI-generated docs for GitHub repos

by izzzzzi

MCP server for codewiki.google: search repos, fetch wiki docs, ask questions

59 installs/wk local only

gitea-mcp

by werebear73

Model Context Protocol server for Gitea (and Forgejo, Codeberg).

241 installs/wk local only

Moxie Docs — questions

Answers built from our own checks of this server.

What can Moxie Docs do?

It exposes 12 tools, read directly from the server on our last check. Among them: moxie.get_ai_context, moxie.get_api_context, moxie.get_conventions, moxie.get_doc_gaps, moxie.get_doc_impact, moxie.get_documentation_opportunities and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Moxie Docs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1089 ms. The bar chart above shows every period we have measured.

How do I connect Moxie Docs?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Moxie Docs need an API key?

No. Moxie Docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Moxie Docs?

It answers our handshake in 1089 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Moxie Docs open source?

Yes — it is published under the MIT licence, written in TypeScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.