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.
Where this stands now
docsagent/docsagent ranks #9 of 1270 tracked Developer Tools items by composite score (8.6 against a section median of 4.9). The section currently carries 1032 Bronze, 134 Silver, 103 Gold, 1 Low Signal. RepoRadar has retained observations for this record since 2026-06-26 (99 days in the current window). Signal extremes versus the section: momentum at the 93th percentile; novelty at the 95th percentile.
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 an MCP server in the Developer Tools section. First seen 2026-06-26; the source record was last checked 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 public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The docsagent/docsagent record combines a 8.6/10 composite score with separate popularity (71.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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.