Notanda (Beta) MCP Server

What the code does

We read the source, 6 d ago · rules ccca72095570

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        env=dict(os.environ),

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        <div class="field small"><label for="c-oa">OA status</label><select id="c-oa">
          <option value="">any</option>${facets.oa_status.map((s) => `<option ${corpusState.filters.oa_status === s ? 'selected' : ''}>${esc(s)}</option>`).join('')}</select></div>

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add notanda -- uvx notanda-mcp

{
  "mcpServers": {
    "notanda": {
      "args": [
        "notanda-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.notanda]
command = "uvx"
args = ["notanda-mcp"]

{
  "mcpServers": {
    "notanda": {
      "args": [
        "notanda-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "notanda": {
      "args": [
        "notanda-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: HARVESTER_OPENALEX_API_KEY (OpenAlex API key used for literature searches.). The author declared them in the registry entry; get the values from the project itself.