Show HN: Nia – MCP server that gives more docs and repos to coding agents
Hacker News (score: 22)Description
Coding agents generate code well but lose accuracy when the answer lives outside the repo in front of them. Developers end up pasting GitHub links, docs, and blog posts by hand and hoping the agent scrolls far enough. Long context windows help, but recent “context rot” measurements show quality still drops as prompts grow. For example, in LongMemEval, all models scored much higher on focused (short, relevant) prompts (~300 tokens) than on full (irrelevant, 113k tokens) prompts, with performance gaps persisting even in the latest models (https://research.trychroma.com/context-rot).
Nia is a MCP that gives more context to any coding agent or IDE. It Indexes multiple repos and docs sites and makes this available via MCP to your coding agent so it has much more context to work with, giving you more specific and accurate answers.
Nia uses a hybrid code search architecture that combines graph-based structural reasoning with vector-based understanding. When a repo or documentation is ingested, Tree-sitter parses it into ASTs across 50+ languages and natural languages, and the code is chunked by function/class boundaries into stable, content-addressable units. These chunks are stored both in a graph db to model relationships like function calls and class inheritance, and in a vector store. At query time, a lightweight agent with give_weight tool dynamically assigns weights between graph and vector search based on intent (e.g., "who calls X" vs "how does auth work"), and both paths are searched in parallel. Results are fused, enriched with full code context, and passed through multi-stage rerankers: semantic reranker, cross-encoders, LLM-based validators.
Early Signal: In internal evals we improved Cursor’s performance by 27 % once Nia had indexed external docs models couldn’t get from their training data or searching the web.
Quickstart: <https://www.youtube.com/watch?v=5019k3Bi8Wo> Demo: <https://www.youtube.com/watch?v=Y-cLJ4N-GDQ>
To try it out: grab an API key at https://app.trynia.ai/ and follow instructions at https://docs.trynia.ai/integrations/nia-mcp.
Try it and break it! I’d love to know which contexts your agent still misses. Corner cases, latency issues, scaling bugs. I’m here 24/7.
Thanks!
More from Hacker
Show HN: Hc: an agentless, multi-tenant shell history sink
Show HN: Hc: an agentless, multi-tenant shell history sink This project is a tool for engineers who live in the terminal and are tired of losing their command history to ephemeral servers or fragmented `.bash_history` files. If you’re jumping between dozens of boxes, many of which might be destroyed an hour later, your "local memory" (the history file) is essentially useless. This tool builds a centralized, permanent brain for your shell activity, ensuring that a complex one-liner you crafted months ago remains accessible even if the server it ran on is long gone.<p>The core mechanism wants to be a "zero-touch" capture that happens at the connection gateway level. Instead of installing logging agents or scripts on every target machine, the tool reconstructs your terminal sessions from raw recording files generated by the proxy you use to connect. This "in-flight" capture means you get a high-fidelity log of every keystroke and output without ever having to touch the configuration of the remote host. It’s a passive way to build a personal knowledge base while you work.<p>To handle the reality of context-switching, the tool is designed with a "multi-tenant" architecture. For an individual engineer, this isn't about managing different users, but about isolating project contexts. It automatically categorizes history based on the specific organization or project tags defined at the gateway. This keeps your work for different clients or personal side-projects in separate buckets, so you don't have to wade through unrelated noise when you're looking for a specific solution.<p>In true nerd fashion, the search interface stays exactly where you want it: in the command line. There is no bloated web UI to slow you down. The tool turns your entire professional history into a searchable, greppable database accessible directly from your terminal.<p>Please read the full story [here](<a href="https://carminatialessandro.blogspot.com/2026/01/hc-agentless-multi-tenant-shell-history.html" rel="nofollow">https://carminatialessandro.blogspot.com/2026/01/hc-agentles...</a>)
Show HN: Ayder – HTTP-native durable event log written in C (curl as client)
Show HN: Ayder – HTTP-native durable event log written in C (curl as client) Hi HN,<p>I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs).<p>There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there.<p>Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg/s sustained (wrk2 @ 50K req/s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets.<p>Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion/streaming workload).
Useful patterns for building HTML tools
Useful patterns for building HTML tools
Migrating to Positron, a next-generation data science IDE for Python and R
Migrating to Positron, a next-generation data science IDE for Python and R
No other tools from this source yet.