DocSlicer

DocSlicer runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/DocSlicer/DocSlicer/releases/download/v0.2.5/docslicer-0.2.5.mcpb version 0.2.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: DOCSLICER_MCP_ROOT (required), DOCSLICER_MCP_ALLOW_CLAUDE_DIR and DOCSLICER_MCP_ALLOW_URLS; set them in the client's configuration for this server.

DocSlicer runs locally from a Python package published to PyPI: docslicer version 0.2.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx docslicer. It reads these environment variables: DOCSLICER_MCP_ROOT (required), DOCSLICER_MCP_ALLOW_CLAUDE_DIR and DOCSLICER_MCP_ALLOW_URLS; set them in the client's configuration for this server. Required arguments: --from.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "docslicer": {
      "command": "uvx",
      "args": [
        "docslicer"
      ],
      "env": {
        "DOCSLICER_MCP_ROOT": "<value>",
        "DOCSLICER_MCP_ALLOW_CLAUDE_DIR": "<value>",
        "DOCSLICER_MCP_ALLOW_URLS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect