search_all
Search all platforms simultaneously
LABSCO SUMMARY
Five sources, one call, when you don't yet know which source has the answer.
The combined search is the reason to attach this rather than five separate servers: at the start of a problem you rarely know whether the answer is a Stack Overflow thread, an MDN page or a package that already does it, and running all five in parallel costs one round trip. The per-platform tools are there for when you do know. Anonymous GitHub search will rate-limit under sustained use, so add a token before relying on it.
What it is
An MCP server that puts the five places a developer actually looks behind one set of tools, so a model researching a problem can reach answers, docs, code and packages without a browser. Results are cached for an hour, so repeated queries during one session do not re-hit the upstream APIs.
What you get
- Stack Overflow questions with scores, answer counts and excerpts —
search_stackoverflow - MDN Web Docs matches with summaries and links, for the web-platform questions where the spec is the answer —
search_mdn - GitHub searched in two passes at once: top repositories by stars, and matching code files with their repository context, optionally filtered to one language —
search_github - npm packages with version, description and download stats, and PyPI packages with version, author and links —
search_npm,search_pypi - All five platforms searched in parallel and returned as one combined result —
search_all
Requirements
No account needed to start: every platform is queried anonymously. A GitHub personal access token in GITHUB_TOKEN is optional and raises the rate limit on the GitHub half. Node.js >= 20.11.0 and npm >= 10.0.0. The npm package name is code-research-server (0.1.0) and it is marked private, so install from a clone with npm install and npm run build. Licensed AGPLv3.
Setup effort
Build from source — git clone https://github.com/jamesjohnsdev/code-research-mcp-server.git
USE CASES
01
Starting on an error message you have never seen
Search all five sources at once and let the results tell you whether this is a known Stack Overflow thread, a documented API behaviour, or a bug someone already patched in a repository.
02
Checking whether a library already exists
Query npm and PyPI for the capability before writing it, and read the download stats and versions to see which candidate is actually maintained.
03
Finding a real implementation, not a snippet
Search GitHub for code in a specific language and get matching files with the repository they came from, so the surrounding context is available.
04
Settling a web-platform question against the docs
Look the API up on MDN and read the summary and link rather than trusting a recollection of how the browser behaves.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
search_github
Search GitHub for repositories and code
search_mdn
Search MDN Web Docs for web development documentation
search_npm
Search npm registry for JavaScript packages
search_pypi
Search PyPI for Python packages
search_stackoverflow
Search Stack Overflow for programming questions and answers
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. search_all runs all five platform searches at once. Results are cached for an hour.
Requires
- Node.js >= 20.11.0
- npm >= 10.0.0
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/jamesjohnsdev/code-research-mcp-server.git
cd code-research-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop, Roo Cline
JSON
{
"mcpServers": {
"code-research": {
"command": "node",
"args": [
"<YOUR_PATH_TO_CODE_RESEARCH_MCP_SERVER>/build/index.js"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
},
"disabled": false,
"alwaysAllow": []
}
}
}
