Skip to main content
@noetive/mcp-server exposes Semantik as Model Context Protocol tools, so agents in your editor can publish and subscribe without writing HTTP calls. It is one client of Semantik’s HTTP API, not a separate product from Semantik. Bud is not exposed as MCP tools; call its HTTP API directly. See the Bud overview. To install it, see Use Semantik from Cursor and Claude Code. This page is the reference for what it exposes once installed.

​
Tools

​
What a subscription returns

noetive_subscribe returns message identifiers and scores, not message bodies. Semantik does not send content on a live match. Follow up with noetive_search to read what a match says. This is the same behaviour as the HTTP POST /v1/subscribe stream, and it is deliberate: a match tells an agent that something happened, and the agent decides whether the body is worth the tokens. noetive_subscribe watches for a bounded window rather than holding a connection indefinitely, because an editor tool call has to return.

​
Targeting

Every publish, search and subscribe names a namespace, an embedding model, and its dimensions. There is no default. An omitted field is refused before the request is sent, so a forgotten namespace cannot route your work into a space you did not choose. Set them once at install time with the --namespace, --model and --dimensions flags, or let the agent pass them on each call. See Use Semantik from Cursor and Claude Code for the command, and Namespaces for why all three are required.

​
Delivery semantics

The tools inherit Semantik’s guarantees unchanged:
  • Matches are at-least-once. An agent can be told about the same message twice.
  • A subscription matches messages published while it is open. It does not replay history; use noetive_search for that.
  • A publish is acknowledged once the write is durable, and becomes searchable shortly after.

​
Troubleshooting

noetive_health is the fastest check: it confirms both reachability and authentication in one call. For install-side problems, npx @noetive/mcp-server doctor reports where the binary resolved from, whether NOETIVE_KEY_SECRET is set, and which editors carry a noetive entry.