Jackalope MCP server
Which servers in the official MCP registry are Jackalope's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-10
- Registry nameio.github.Jackalope-Dev/moxie-docspublished by Jackalope-Dev on GitHub
Published under the GitHub organisation Jackalope-Dev, the same one jackalope.dev links from its homepage. The registry ties that namespace to a GitHub sign-in.
- Stateanswerschecked 2026-10-10
- Tools12
- Server calls itselfmoxie-docs
- Server version0.4.0
- Protocol version2025-06-18
On 2026-10-10 the server answered initialize and tools/list without a sign-in. First answer in 2076 ms.
moxie.get_conventionsGet 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…
moxie.search_docsKeyword 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…
moxie.list_docsList 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…
moxie.get_doc_gapsList 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…
moxie.get_documentation_opportunitiesList 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…
moxie.get_documentation_patternsGet 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…
moxie.get_ai_contextGet 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…
moxie.get_doc_impactGiven 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…
moxie.get_api_contextGiven 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…
moxie.review_changeSelf-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…
moxie.propose_doc_updatePropose 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 +…
moxie.propose_doc_removalPropose 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"moxie-docs": {
"type": "http",
"url": "https://moxiedocs.com/api/mcp"
}
}
}- io.github.Jackalope-Dev/allmcps-servernot asked yetpublished by Jackalope-Dev on GitHub
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.