home / mcp / all-in-mcp mcp server

All-in-MCP MCP Server

Provides academic paper search, web search, and PDF processing via a modular MCP server.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "isomoes-all-in-mcp": {
      "command": "pipx",
      "args": [
        "run",
        "all-in-mcp"
      ],
      "env": {
        "APAPER": "true",
        "QWEN_SEARCH": "true",
        "GITHUB_REPO_MCP": "true",
        "DASHSCOPE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

All-in-MCP is a FastMCP-based server that combines academic paper search, web search, and PDF processing utilities into a modular, scalable MCP server. It provides a proxy that routes requests to specialized tools and supports standalone tool servers for focused use cases, enabling you to search papers, perform web queries, and work with PDFs from a single MCP-enabled workflow.

How to use

You interact with All-in-MCP through an MCP client, sending requests to the available MCP endpoints exposed by the proxy server or to the standalone tool servers. Use the client to search academic papers, fetch PDFs, extract text from PDFs, and perform web searches. Tools are registered automatically, so you can discover and call them through your MCP client configuration without manual tool registration.

How to install

Prerequisites you need before installing and running All-in-MCP:

Python 3.10 or higher

pipx for Python package installation

npx for MCP Inspector (Node.js required)

Step-by-step installation and start flow

# Install the main All-in-MCP package via pipx
pipx install all-in-mcp

# If you want to run the standalone APaper server
pipx run apaper

# If you want to run the standalone Qwen Search server
DASHSCOPE_API_KEY=your_api_key_here pipx run qwen-search

# Run the all-in-MCP proxy with APaper, Qwen Search, and GitHub repo tools enabled
APAPER=true QWEN_SEARCH=true DASHSCOPE_API_KEY=your_api_key_here GITHUB_REPO_MCP=true pipx run all-in-mcp

Additional setup and ongoing usage

You can also verify functionality and explore tool schemas using the MCP Inspector during development and testing. The inspector lets you interactively test tools, view server capabilities, and monitor debug messages to understand how FastMCP endpoints behave.

Server options and environments

The main proxy server can enable or disable backends through environment variables. For example, you can enable APaper tools, Qwen web search, and GitHub repository tools by setting environment variables when starting the proxy.

Examples of entry points you will use in your MCP client configuration are shown in the following runtime configurations. Use these exact commands to start the servers.

Troubleshooting and notes

If you encounter issues, use the MCP Inspector to test tools with real parameters and monitor server messages. Ensure that required API keys are set for Dashscope (DASH SCOPE) and that the APaper and GitHub repository endpoints are correctly enabled when starting the proxy.

Available tools

apaper_search_iacr_papers

Search academic papers from IACR ePrint Archive using the APaper module

apaper_download_iacr_paper

Download PDF of an IACR ePrint paper from the APaper module

apaper_read_iacr_paper

Read and extract text content from an IACR ePrint paper PDF via APaper

apaper_search_dblp_papers

Search DBLP computer science bibliography database via APaper

apaper_search_google_scholar_papers

Search academic papers across disciplines with citation data via APaper

qwen_search_web_search

Search the web using Qwen/Dashscope API via Qwen Search module

github-repo-mcp_getRepoAllDirectories

Get all directories from a GitHub repository via GitHub MCP module

github-repo-mcp_getRepoDirectories

Get directories from a specific path in a GitHub repository via GitHub MCP module

github-repo-mcp_getRepoFile

Get file content from a GitHub repository via GitHub MCP module