All In MCP Server

A FastMCP-based Model Context Protocol (MCP) server providing academic paper search, web search, and PDF processing utilities. Features a modular

Local serverstdioPython

What is the All In MCP MCP server?

All In MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A FastMCP-based Model Context Protocol (MCP) server providing academic paper search, web search, and PDF processing utilities. Features a modular architecture with both proxy and standalone server capabilities.

What the assistant can call

Once All In MCP is connected, these are the calls the assistant has available:

  • Category — Tool Name
  • Prerequisites — The Prerequisites tool exposed by this server

Configuration and credentials

You will need 4 environment variables: APAPER, QWEN_SEARCH, DASHSCOPE_API_KEY, GITHUB_REPO_MCP. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Python 3.10 or higher - pipx for Python package installation - npx for MCP Inspector (Node.js required)

Setting it up

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. All In MCP's toolset — Category, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by jiahaoxiang2000; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the all in mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryTool Name
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the All In MCP MCP server

{
  "mcpServers": {
    "all-in": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "APAPER": "your-value",
        "QWEN_SEARCH": "your-value",
        "DASHSCOPE_API_KEY": "your-value",
        "GITHUB_REPO_MCP": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Python 3.10 or higher - pipx for Python package installation - npx for MCP Inspector (Node.js required)
VariableDescriptionRequired
APAPERConfiguration value read at startup.Optional
QWEN_SEARCHConfiguration value read at startup.Optional
DASHSCOPE_API_KEYCredential the server authenticates with.Yes
GITHUB_REPO_MCPConfiguration value read at startup.Optional

Example prompts to try

  • Use All In MCP to Category.
  • Use All In MCP to Prerequisites.

Frequently asked questions

It connects All In MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Category, Prerequisites) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with All In MCP directly.