Developer Tools Mcp Server

io.github.TheNextGenNexusPublished by GitHub account TheNextGenNexusv1.0.1Updated Oct 24, 2026

Access GitHub repos, npm/PyPI packages, Stack Overflow, arXiv, and Google Scholar

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that lets an assistant look up GitHub repos, npm and PyPI packages, Stack Overflow, arXiv and Google Scholar via Apify.

What you can do
  • Look up and search GitHub repositories by keyword or by name
  • Fetch npm and PyPI package details and download stats
  • Search Stack Overflow questions
  • Search arXiv and Google Scholar for academic papers
  • Forward each request to the nexgendata Apify endpoint and return the results
When to use it
Useful when you want an assistant to research open-source libraries, check package details and popularity, find answers to coding questions, or gather academic references without leaving the chat.
Requirements
Runs locally over stdio, typically launched with npx from the npm package, so Node.js and network access are needed. An Apify API token in APIFY_TOKEN is optional; without it the server uses a rate-limited public endpoint.
Before you install
All tool calls are forwarded to a third-party Apify endpoint, so queries leave your machine. The APIFY_TOKEN secret grants authenticated access and should be kept private. The README's npx package name differs from the manifest's package name, so verify which package you install.

Installation

In SourceWeft

  1. Open Developer Tools Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Developer Tools MCP Server

Access GitHub repos, npm/PyPI packages, Stack Overflow, arXiv, and Google Scholar — powered by nexgendata on Apify.

Quick Start

Using npx (recommended)

bash
npx @nexgendata/developer-tools-mcp-server

Install globally

bash
npm install -g @nexgendata/developer-tools-mcp-server

Configure with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{      "mcpServers": {            "developer-tools-mcp-server": {                  "command": "npx",                  "args": [                        "-y",                        "@nexgendata/developer-tools-mcp-server"                  ],                  "env": {                        "APIFY_TOKEN": "your-apify-token-optional"                  }            }      }}

Configure with Cline

Add the same configuration to your Cline MCP settings.

Available Tools

ToolDescription
get_github_repoGet detailed information about a GitHub repository
search_githubSearch GitHub repositories by keyword
get_npm_packageGet npm package details and stats
get_pypi_packageGet PyPI package details and stats
search_stackoverflowSearch Stack Overflow questions
search_arxiv_papersSearch arXiv for research papers
search_scholarSearch Google Scholar for academic papers

Environment Variables

VariableRequiredDescription
APIFY_TOKENNoYour Apify API token for authenticated access. Without it, the server uses the public endpoint (rate-limited).

How It Works

This MCP server acts as a local stdio bridge to the nexgendata Apify MCP endpoint. When you call a tool, it forwards the request to Apify and returns the results.

Links

License

MIT

Source: servers/developer-tools-mcp-server/README.md at commit 38fefb7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.