# developer-tools-mcp-server [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://apify.com/nexgendata/developer-tools-mcp-server  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/developer-tools-mcp-server

## Description
Search GitHub, npm, PyPI, StackOverflow, ArXiv from one MCP — built for coding agents.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "developer-tools-mcp-server": {
    "command": "npx",
    "args": ["-y","developer-tools-mcp-server"]
  }
}
```

## Documentation

## What developer-tools-mcp-server MCP server does

The developer-tools-mcp-server MCP server provides a single MCP entry point for searching five sources: GitHub, npm, PyPI, StackOverflow, and ArXiv. Its stated purpose is to support coding agents that need to locate implementation examples, package information, developer questions, or academic material without using separate source-specific MCP servers.

The supported sources cover several common parts of software development. GitHub can provide repository and code-related search results. npm and PyPI cover JavaScript and Python package ecosystems. StackOverflow represents developer questions and answers, while ArXiv provides access to research literature. The available description does not specify the exact fields returned, ranking behavior, filters, or whether searches support pagination.

## How it works

The developer-tools-mcp-server MCP server exposes the listed search destinations through the Model Context Protocol. An MCP-compatible coding agent can use that shared interface to search across the available services. The source material does not identify separate tool names or describe whether a query can target one source or multiple sources at once, so those details should be confirmed before implementation.

This design is relevant when an agent must investigate a programming problem across documentation-adjacent sources, package registries, code-hosting content, community discussions, and research papers. It may also reduce the need to configure a separate integration for each listed destination, although the provided material does not describe its internal architecture or request handling.

## Tools and capabilities

The documented capability is search across:

- GitHub
- npm
- PyPI
- StackOverflow
- ArXiv

The listing describes the project as built for coding agents, making developer research the clearest supported use case. It does not document write operations, repository mutation, package publishing, question posting, or any other action beyond searching.

## Limitations and notes

The developer-tools-mcp-server MCP server has no available README in the supplied material. As a result, installation steps, runtime requirements, authentication requirements, environment variables, licensing, supported MCP clients, and detailed tool schemas cannot be confirmed from this listing. The source also does not state whether the connected services require individual credentials or whether the server manages access on the user’s behalf.

Treat the five named sources as the confirmed scope. Validate setup, query syntax, response formats, rate limits, and client configuration against the project’s current documentation before deploying it in a coding-agent workflow.

_Full upstream README: https://allmcps.com/mcp/developer-tools-mcp-server/readme_