Noetive MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

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.

postinstall: node postinstall.js

  const child = spawn(binary, argv, { stdio: "inherit" });

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.

            body, err := os.ReadFile(filepath.Join(dir, "prompts", source))

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 mcp-server -e 'NOETIVE_KEY_SECRET=<NOETIVE_KEY_SECRET>' -- npx -y @noetive/mcp-server

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@noetive/mcp-server"
      ],
      "env": {
        "NOETIVE_KEY_SECRET": "<NOETIVE_KEY_SECRET>"
      }
    }
  }
}

[mcp_servers.mcp-server]
command = "npx"
args = ["-y", "@noetive/mcp-server"]
env = { NOETIVE_KEY_SECRET = "<NOETIVE_KEY_SECRET>" }

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@noetive/mcp-server"
      ],
      "env": {
        "NOETIVE_KEY_SECRET": "<NOETIVE_KEY_SECRET>"
      }
    }
  }
}

{
  "servers": {
    "mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@noetive/mcp-server"
      ],
      "env": {
        "NOETIVE_KEY_SECRET": "<NOETIVE_KEY_SECRET>"
      }
    }
  }
}

Put your own value in place of <NOETIVE_KEY_SECRET> (API key from the Noetive dashboard. Every tool reaches Noetive, so every tool needs it. Without it the server still starts and registers its tools, and each one explains what is missing). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: NOETIVE_NAMESPACE (Namespace used when a tool call does not name one. There is no default; without this, every call must name a namespace), NOETIVE_MODEL (Embedding model used when a tool call does not name one, for example Qwen3-Embedding-4B), NOETIVE_DIMENSIONS (Embedding dimensionality used when a tool call does not name one, for example 1024. Must match the model), NOETIVE_DISABLE_GLOBAL_NS (Set to 1 to close the shared "global" namespace on this server. Every call that routes there is refused before the request is sent, and the tools stop offering it as an example. Unset leaves it available. A value that is neither a yes nor a no stops the server rather than being read as no), NOETIVE_EMBEDDINGS_URL (An OpenAI-compatible /v1/embeddings endpoint you run. Set it and embeddings are computed on this machine rather than by Noetive: a publish carries the vector alongside its text, and a query's anchor phrases are replaced by vectors so they are never sent. This is not confidential publishing: message text still travels, because that is what a search returns. The endpoint must answer to the same model name as NOETIVE_MODEL and return NOETIVE_DIMENSIONS values. Plain http is accepted only for a loopback address. Inside a container 127.0.0.1 is the container itself; use host.docker.internal), NOETIVE_EMBEDDINGS_KEY_SECRET (Bearer token for that endpoint, when it needs one. Endpoints running on your own machine usually do not).