Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
MCPpedia last refreshed this data
io.github.Jackalope-Dev/moxie-docs is an MCP server that living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge. Its tool list has not been published yet over http, requires no API key, and scores 85/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"moxie-docs": {
"url": "https://moxiedocs.com/api/mcp",
"headers": {
"Authorization": "Bearer <MOXIE_TOKEN>"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked moxie-docs against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Jackalope-Dev/moxie-docs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The Moxie Docs Model Context Protocol (MCP) server, the agent skills Moxie Docs installs into your repository, and the moxie-docs CLI that wires it all up — npx moxie-docs setup.
This repo is also the open-source home of the moxie-docs npm package: a setup CLI plus the MCP interface (tool catalog, prompts, server metadata, and skill renderers) you can import. The hosted server, indexing pipeline, and your generated docs stay in the private Moxie Docs service.
Moxie Docs indexes a connected GitHub repository and keeps its documentation alive — generating docs, discovering conventions, tracking documentation gaps and drift, and opening pull requests that keep docs in sync with code. The MCP server exposes that living context to coding agents (Claude Code, Cursor, VS Code, Codex, and any MCP-capable client) so they ground their work in how your repository actually does things — and keep the docs current as they change code.
https://moxiedocs.com/api/mcpThis repository is documentation and distribution assets only. The hosted server, indexing pipeline, and your repositories' documentation are not stored here.
The fastest path — from your repository's directory:
npx moxie-docs setup
This signs you in (OAuth in your browser), writes the MCP config for your editor, installs the moxie-docs skill + AGENTS.md guidance, and verifies the connection. After that, your agent reads live context with moxie.get_ai_context before editing and proposes doc updates that land in the same PR.
Prefer to do it by hand? Connect a repository at https://moxiedocs.com, then add the server to your agent with a config block.
The moxie-docs CLI (Node ≥ 18, zero runtime dependencies) sets up and manages the connection. Run it with npx moxie-docs <command> or install it globally (npm i -g moxie-docs).
| Command | What it does |
|---|---|
moxie-docs setup | End-to-end: sign in, configure your MCP client, install the skill + AGENTS.md block, and smoke-test. |
moxie-docs login | Sign in via the browser (OAuth 2.1 + PKCE) and store credentials in ~/.moxie-docs/. |
moxie-docs status | Show your scope, connected repositories, and available tool count. |
moxie-docs config <client> | Write the moxie-docs server entry into a client config (claude-code, cursor |