All servers · Code & repositories
io.github.vanshulgoyal101/ctx
io.github.vanshulgoyal101/ctx · v1.0.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 6 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.
Connect
streamable-http · https://ctx.vanshul.com/mcp
claude mcp add --transport http ctx https://ctx.vanshul.com/mcp{
"mcpServers": {
"ctx": {
"url": "https://ctx.vanshul.com/mcp"
}
}
}Tools as reported by the server
pack_repoFetch a GitHub repository and return it as one agent-ready context blob: text files concatenated with clear "==== path ====" headers, binaries/lockfiles/build dirs stripped, with a token estimate. Use include/exclude globs to focus, and max_tokens to fit a budget.search_contextSearch a GitHub repository and return only the passages that match a query — each with its file path, line number and a relevance score. Far more token-efficient than pack_repo when you need a specific detail (e.g. "where is auth handled?").list_filesList the text files ctx would include for a repository (after stripping binaries, lockfiles and build dirs), with their byte sizes. Cheap way for an agent to see the layout before packing.get_fileReturn the full text of a single file in a repository, by path. Use after list_files or search_context to drill in.pack_docsCrawl a documentation site from a start URL and return it as one agent-ready context blob: each page extracted to clean Markdown, concatenated with its URL. Stays within the same site section; bounded by depth and page count. Use max_tokens to fit a budget.search_docsCrawl a documentation site and return only the passages that match a query — each with its page URL, line and a relevance score. Token-efficient way to answer a question from docs without packing the whole site.
Repository · Website · JSON · Text for agents · Registry updated 2026-08-06