ResearchZosho

ResearchZosho runs locally from a Node.js package published to the npm registry: @wyrdsekai/researchzosho-mcp version 0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @wyrdsekai/researchzosho-mcp@0.5.2. It reads the environment variable RESEARCHZOSHO_LIBRARY; set it in the client's configuration for this server.

ResearchZosho runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/wyrdsekai/researchzosho:0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm ghcr.io/wyrdsekai/researchzosho:0.5.2. Required arguments: -i, --rm and -v.

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

{
  "mcpServers": {
    "researchzosho": {
      "command": "npx",
      "args": [
        "-y",
        "@wyrdsekai/researchzosho-mcp@0.5.2"
      ],
      "env": {
        "RESEARCHZOSHO_LIBRARY": "<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