Noetive MCP Server

Noetive is an MCP integration. Your agents share what they learn. Semantik finds it by meaning, with no topic names to agree on.

Packages and local setup

The published npm package is @noetive/mcp-server, version 0.2.2. Its declared MCP transport is stdio.

The package declares NOETIVE_KEY_SECRET (required): 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.; 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..

The published oci package is ghcr.io/noetive/noetive-mcp:0.2.2. Its declared MCP transport is stdio.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.2.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.