io.github.SK-DEV-AI/codesearch

Official registry Developer tools

Code, package, docs, paper and vulnerability search. 17 tools, keyless lanes.

What can you do with io.github.SK-DEV-AI/codesearch?

  • analyze — Start here for unfamiliar repos: GitHub metadata + code quality + wiki architecture in one call (10–15s).
  • search_all — Broad multi-source discovery (Context7, GitHub, DeepWiki, CodeWiki, SO, HN, Libraries.io, npm, DevDocs, Semantic Scholar, Tavily…). For surgical single-source work call the tool below directly.
  • code_search — Search code/docs/symbols across indexed dependencies (target=npm:express). npm/PyPI/crates only — for GitHub repos use searchcode or analyze.
  • code_files / code_read — List files / read a file in an indexed dependency by package spec.
  • searchcode — Per-repo intelligence: analyze (overview), search (code within the repo), findings (quality issues), file_tree, get_file. Needs repository for every action. Free, no auth.
  • wiki — Repo architecture Q&A via DeepWiki + CodeWiki. Single repo (owner+repo) or up to 10 repos (repos).
  • search_package — Raw registry queries: versions, dist-tags, deps.dev graphs, advisories (version='latest' OK). For composite intelligence use pkg.
  • pkg — Composite package intelligence: metadata, changelog, upgrade review (vulns + changelog + deps diff), file list/read.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package skdev-codesearch-mcp
Claude Code
claude mcp add codesearch -e 'GROQ_API_KEYS=<your groq_api_keys>' -e 'TAVILY_KEYS=<your tavily_keys>' -e 'NV_KEY=<your nv_key>' -e 'SE_KEY=<your se_key>' -e 'S2_KEY=<your s2_key>' -- uvx skdev-codesearch-mcp==1.0.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "codesearch": {
            "command": "uvx",
            "args": [
                "skdev-codesearch-mcp==1.0.1"
            ],
            "env": {
                "GROQ_API_KEYS": "<your groq_api_keys>",
                "TAVILY_KEYS": "<your tavily_keys>",
                "NV_KEY": "<your nv_key>",
                "SE_KEY": "<your se_key>",
                "S2_KEY": "<your s2_key>"
            }
        }
    }
}

Environment variables

  • GROQ_API_KEYS secret Optional. Groq keys for synthesis and query rewriting.
  • TAVILY_KEYS secret Optional. Tavily search lane.
  • NV_KEY secret Optional. NVIDIA embeddings for ranking.
  • SE_KEY secret Optional. Stack Exchange key (10k/day instead of 300).
  • S2_KEY secret Optional. Semantic Scholar key (1 RPS).

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. codesearch MCP Server
  2. Tools (17)
  3. Setup
  4. Install from PyPI
  5. Docker
  6. Notes

codesearch MCP Server

mcp-name: io.github.SK-DEV-AI/codesearch

Companion agent skills: SK-DEV-AI/skills · npx skills add SK-DEV-AI/skills

Code, package, docs, and paper search MCP server. Per-package source navigation (npm/PyPI/crates), per-repo intelligence (GitHub URL or owner/repo), Q&A communities, vulnerability data, documentation, and academic papers — with embedding dedup and a local cross-encoder reranker.

Tools (17)

  • analyze — Start here for unfamiliar repos: GitHub metadata + code quality + wiki architecture in one call (10–15s).
  • search_all — Broad multi-source discovery (Context7, GitHub, DeepWiki, CodeWiki, SO, HN, Libraries.io, npm, DevDocs, Semantic Scholar, Tavily…). For surgical single-source work call the tool below directly.
  • code_search — Search code/docs/symbols across indexed dependencies (target=npm:express). npm/PyPI/crates only — for GitHub repos use searchcode or analyze.
  • code_files / code_read — List files / read a file in an indexed dependency by package spec.
  • searchcode — Per-repo intelligence: analyze (overview), search (code within the repo), findings (quality issues), file_tree, get_file. Needs repository for every action. Free, no auth.
  • wiki — Repo architecture Q&A via DeepWiki + CodeWiki. Single repo (owner+repo) or up to 10 repos (repos).
  • search_package — Raw registry queries: versions, dist-tags, deps.dev graphs, advisories (version='latest' OK). For composite intelligence use pkg.
  • pkg — Composite package intelligence: metadata, changelog, upgrade review (vulns + changelog + deps diff), file list/read.
  • search_libraries — Libraries.io metadata and source rank. Compare dependency candidates, find the repo behind a package.
  • vulns — Sonatype Guide + keyless OSV.dev fallback: scan (needs platform+name+version), detail (needs vuln_id; enriched with NVD CVSS/CWE/references), latest_version/license (need purl).
  • docs — Docs with smart fallback (Context7 → ReadTheDocs → llms.txt → DevDocs); then fetch(url) or devdocs_fetch_content for full pages.
  • so_search — Stack Overflow: stackexchange (authoritative resolved answers) or sofa (fresher agent content, needs SOFA_KEY).
  • hn — Hacker News discussion and sentiment (search, stories, items, users).
  • papers — Academic papers. Prefer action=search (S2 → arXiv → OpenAlex → CORE fallback chain); arxiv_search is single-source and rate-limited.
  • enrich — Fetch full content for a result list from any search tool, dedup + rerank.
  • ping — Connectivity check. Use before expensive calls when uncertain.

Setup

Requires Python 3.14+.

python3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
cp run.example run   # fill in your API keys (run is gitignored — never commit it)
chmod +x run

Point your MCP client at run (stdio):

{ "codesearch": { "command": "/path/to/codesearch/run" } }
API keys (run)
KeyUsed forRequired?
GITHUB_TOKENGitHub API (repo ops, higher rate limits)Recommended
CONTEXT7_API_KEYContext7 docsOptional
TAVILY_KEYSTavily lane in search_allOptional
S2_API_KEYSemantic Scholar (1 rps dedicated vs shared anonymous pool)Optional
SE_API_KEY / SOFA_KEYStack Exchange / Stack Overflow for AgentsOptional
LI_KEYLibraries.ioOptional
OSS_TOKENSonatype OSS IndexOptional
FIRECRAWL_KEYSFirecrawl fallbackOptional
NV_KEYNVIDIA embedding endpointOptional

Install from PyPI

pip install skdev-codesearch-mcp          # core install, small
pip install skdev-codesearch-mcp[all]     # + browser/OCR/extract extras (multi-GB)

The codesearch-mcp console script speaks MCP over stdio:

{ "codesearch": { "command": "codesearch-mcp" } }

Docker

docker build -t codesearch-mcp .
docker run --rm -i codesearch-mcp

Keys are passed at run time, never baked in: -e GROQ_API_KEYS=.... Heavy extras: docker build --build-arg EXTRAS="[all]" -t codesearch-mcp .

Notes

  • Reranker (optional, local): shared with the websearch server — one cross-encoder worker over a Unix socket. Without it, results return unranked; everything still works.
  • Caching: per-source file caches with TTLs; repeat queries are cheap.
  • Safety: all user-URL fetches are SSRF-validated (private-IP blocking + redirect-hop revalidation).

Frequently asked questions

What is io.github.SK-DEV-AI/codesearch?

Code, package, docs, paper and vulnerability search. 17 tools, keyless lanes.

How do I install io.github.SK-DEV-AI/codesearch?

It runs on your machine. In Claude Code: claude mcp add codesearch -e 'GROQ_API_KEYS=<your groq_api_keys>' -e 'TAVILY_KEYS=<your tavily_keys>' -e 'NV_KEY=<your nv_key>' -e 'SE_KEY=<your se_key>' -e 'S2_KEY=<your s2_key>' -- uvx skdev-codesearch-mcp==1.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.SK-DEV-AI/codesearch need an API key?

Yes. It expects GROQ_API_KEYS, TAVILY_KEYS, NV_KEY, SE_KEY, S2_KEY, which you set in its configuration.

Is io.github.SK-DEV-AI/codesearch open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.SK-DEV-AI/codesearch?

It is published by SK-DEV-AI. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.