Server definition
- Hash
- sha256:455a666c0fe46bfa26350d9811fc1645af6b41a24e2343299f933671d07fa69b
- What it is
- What a remote MCP server returned when asked what it offers: 12 tools
The blob, as servednamed by its sha256
{
"instructions": "Use Moxie Docs BEFORE writing code so any required documentation updates land in the same pull request as the change.\n\nRecommended flow:\n1. Call `moxie.get_ai_context` to load repo status, verified commands, top conventions, and open gaps.\n2. Before editing a file, call `moxie.get_doc_impact` with the file paths you intend to change. It returns the docs/gaps/conventions that apply AND flags paths that are net-new or undocumented (e.g. a new API surface) so you can document them in the same PR.\n3. Use `moxie.get_documentation_patterns` to decide where new docs belong, and `moxie.get_conventions` for category-specific rules.\n4. After you make the change and BEFORE you commit, call `moxie.review_change` with the new contents of the files you changed (and any deletedPaths). It flags convention breaches, docs your change makes false, undocumented new surface, and broken references. Fix every must-fix finding and re-run until the verdict is clean.\n5. When you add or update a doc, call `moxie.propose_doc_update` with the title, markdown, and either a target path or the slug of an existing doc. It returns the exact repository-relative path and content to WRITE INTO YOUR OWN BRANCH and commit, so the docs land in this same PR. Moxie does not open a separate PR.\n6. Whenever you edit an existing doc, read the whole file and fix anything else your change makes stale or wrong: correct statements your change contradicts, complete lists or tables it makes incomplete, and drop references to code that no longer exists. A doc you touch should be fully correct when you commit it - leaving a known-outdated section beside a fresh update is not acceptable.\n7. Run the verified commands before opening or updating a PR.\n\nTokens are organization-wide, so always pass `repository: \"owner/name\"` (case-insensitive) on every tool call unless your token is scoped to a single repository. Do not invent documentation: only create or expand human docs when behavior, API, workflow, architecture, or operational contract changed. This guardrail forbids fabricating new docs - it does not excuse leaving stale or contradicted content in a file you are already editing; correcting that is always in scope.",
"tools": [
{
"description": "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.",
"inputSchema": {
"properties": {
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.get_ai_context",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"paths": {
"description": "Repository-relative file paths to inspect for API endpoint context.",
"items": {
"type": "string"
},
"type": "array"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.get_api_context",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"category": {
"description": "Optional category filter, such as testing, structure, docs, or review.",
"type": "string"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.get_conventions",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
},
"severity": {
"description": "Optional severity filter: high, medium, low, or info.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.get_doc_gaps",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"changedPaths": {
"description": "Repository-relative file paths the agent intends to modify (e.g., apps/web/src/app/api/billing/webhook/route.ts).",
"items": {
"type": "string"
},
"type": "array"
},
"deletedPaths": {
"description": "Subset of paths that are being DELETED. Moxie flags any doc whose every cited source path is in this list as a removal candidate for moxie.propose_doc_removal.",
"items": {
"type": "string"
},
"type": "array"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"required": [
"changedPaths"
],
"type": "object"
},
"name": "moxie.get_doc_impact",
"outputSchema": null
},
{
"description": "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).",
"inputSchema": {
"properties": {
"kind": {
"description": "Optional kind filter: documentation_gap, documentation_drift, or pr_template.",
"type": "string"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
},
"severity": {
"description": "Optional severity filter: high, medium, low, or info.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.get_documentation_opportunities",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.get_documentation_patterns",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"limit": {
"description": "Maximum docs to return (1-200, default 50).",
"type": "number"
},
"offset": {
"description": "Number of docs to skip for pagination (default 0). Use the cursor in the response to fetch the next page.",
"type": "number"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
},
"section": {
"description": "Optional section/collection filter (case-insensitive substring), e.g. \"Backend\" or \"Billing\". Omit to list every section.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.list_docs",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"reason": {
"description": "Why this doc is no longer relevant.",
"type": "string"
},
"removedSourcePaths": {
"description": "Code paths being deleted that made this doc irrelevant, for provenance.",
"items": {
"type": "string"
},
"type": "array"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
},
"slug": {
"description": "Slug of the existing generated doc to remove.",
"type": "string"
},
"targetPath": {
"description": "Repository-relative path of the doc to remove (must be a Moxie-tracked doc). Use instead of slug.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.propose_doc_removal",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"baseSlug": {
"description": "Slug of an existing generated doc to update instead of supplying targetPath.",
"type": "string"
},
"markdown": {
"description": "The documentation content (Markdown) to write to the target file.",
"type": "string"
},
"reason": {
"description": "Why this doc is being added or changed.",
"type": "string"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
},
"sourcePaths": {
"description": "Code paths this doc documents, for provenance.",
"items": {
"type": "string"
},
"type": "array"
},
"targetPath": {
"description": "Repository-relative path to write the doc to (e.g., docs/billing.md). Omit to resolve from baseSlug.",
"type": "string"
},
"title": {
"description": "Short human title for the documentation update.",
"type": "string"
}
},
"required": [
"title",
"markdown"
],
"type": "object"
},
"name": "moxie.propose_doc_update",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"changedFiles": {
"description": "The files your change adds or modifies, in their PROPOSED new state. Provide newContent (the full new file text) for each; you may also/instead provide patch (a unified diff). Max 20 files per call.",
"items": {
"properties": {
"newContent": {
"description": "The full new contents of the file after your change.",
"type": "string"
},
"patch": {
"description": "Optional unified diff for the file (used if newContent is omitted).",
"type": "string"
},
"path": {
"description": "Repository-relative path, e.g. apps/web/src/app/api/foo/route.ts.",
"type": "string"
},
"status": {
"description": "Either \"added\" or \"modified\".",
"type": "string"
}
},
"required": [
"path"
],
"type": "object"
},
"type": "array"
},
"deletedPaths": {
"description": "Repository-relative paths your change DELETES, so Moxie can flag docs whose references break.",
"items": {
"type": "string"
},
"type": "array"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"required": [
"changedFiles"
],
"type": "object"
},
"name": "moxie.review_change",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"properties": {
"limit": {
"description": "Maximum matches to return (1-20, default 8).",
"type": "number"
},
"query": {
"description": "Search phrase or topic. Omit to return recent context for the repository.",
"type": "string"
},
"repository": {
"description": "The target repository as \"owner/name\" (e.g. \"acme/app\"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.",
"type": "string"
}
},
"type": "object"
},
"name": "moxie.search_docs",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:455a666c0fe46bfa26350d9811fc1645af6b41a24e2343299f933671d07fa69b | sha256sum