Arimxyer Doc Manager Mcp
arimxyer-doc-manager-mcp is a Claude Code plugin for the Build phase that connects an MCP server for documentation lifecycle automation including link checks, change detection, and quality assessment.
by arimxyer · github.com/arimxyer/doc-manager-mcp
Register the MCP plugin when you want an agent to manage doc health—broken links, change detection, quality checks, and sync—across a real repo.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install arimxyer-doc-manager-mcp@arimxyer/doc-manager-mcpBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:arimxyer/doc-manager-mcp") and the paste-ready config with skillselion.get_install_config("plugin:arimxyer/doc-manager-mcp").
What it does
arimxyer-doc-manager-mcp is a Claude Code plugin that exposes a Model Context Protocol server built for documentation lifecycle management on software projects. Solo builders who ship fast often let READMEs, API references, and runbooks fall behind the code; this plugin gives the agent structured tools to detect those gaps, validate links, score doc quality, and synchronize documentation with the current tree instead of one-off grep sessions. It is strongest during active build when you are editing features and docs together, but the same checks matter at ship review and when you iterate in production. You should expect MCP configuration in Claude Code and a repo with markdown or mixed doc assets—not a hosted wiki replacement. One plugin bundles the server; complexity is intermediate because you need to understand which MCP tools map to your doc layout and CI habits.
Highlights
- MCP server for end-to-end documentation lifecycle management
- Automated change detection when code and docs diverge
- Link validation and documentation quality assessment workflows
- Documentation synchronization for software projects
- Agent-oriented monitoring and coordination hooks for doc maintenance
Why builders use it
Documentation rots silently while you ship features, and manual link checks do not scale for a one-person codebase.
After install, your agent can run MCP-driven doc health workflows—validation, assessment, and sync—on demand or as part of your ship checklist.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 6 stars, 0 votes.
FAQ
Who is arimxyer-doc-manager-mcp for?
Developers using Claude Code who maintain project documentation in-repo and want automated change detection, link validation, and quality checks via MCP.
When should I use arimxyer-doc-manager-mcp?
Use it while building and documenting features, before release when reviewing doc accuracy, and during operate iterations when code changes outpace docs.
How do I add arimxyer-doc-manager-mcp to my agent?
Add the plugin from arimxyer/doc-manager-mcp, register the MCP server in Claude Code per the repository instructions, and point it at your project documentation roots.
Comments
Share how you use arimxyer-doc-manager-mcp, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.