Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people who want agents to work against real local documents instead of copying files into chat or standing up a heavier enterprise knowledge stack first.
Who should use it
Who should skip it
Pass on docsagent/docsagent if its scope or audience does not match what your team is building right now.
About this signal
docsagent/docsagent is tracked by RepoRadar as a mcp server in the Developer Tools section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, docsagent/docsagent is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned docsagent/docsagent a composite score of 8.6 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 71.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It indexes and exposes local document contents to agents, so start with a tightly scoped folder before pointing it at sensitive archives; Apache-2.0 is declared in package metadata but the repo root currently lacks a LICENSE file, so license-sensitive teams should verify the published package before broader rollout; Parsing quality still depends on the source files, so test search and retrieval on representative PDFs and Office docs before trusting automated answers.