Skip to content
LogoLogo

Nebula has two distinct Model Context Protocol integrations. Their tools, authentication, and collection scope are not interchangeable.

Generated SDK MCP server

The @nebula-ai/mcp-server package exposes:

  • search_docs: find operations in the generated Nebula SDK documentation.
  • execute: run trusted JavaScript against an authenticated TypeScript SDK client.

The SDK and operation documentation derive from the public OpenAPI contract. Tool definitions and transports belong to the MCP runtime; this server does not register add_memory or search_memories.

Use search_docs to find memory.store or memory.search, then call the SDK through execute. Memory search uses effort to control retrieval work, not a limit result-count parameter. The optional limit on search_docs only bounds documentation matches. See Search.

Connect and authenticate

Use a package release qualified for your deployment's API version. See the MCP package instructions for startup and transport options; a published package version alone does not establish compatibility with the public v2 API.

  • Stdio uses NEBULA_API_KEY.
  • Streamable HTTP uses an Authorization: Bearer ... API key on each request.
  • Custom deployments must configure both NEBULA_BASE_URL and NEBULA_API_KEY_EXCHANGE_URL; a partial override is rejected.

The SDK selects a collection for each operation, subject to the key's authorization. This server does not bind the connection to one collection through X-Collection-ID.

Legacy hosted MCP

Existing hosted connections configured through Nebula use the legacy add_memory and search_memories tools and select one collection with X-Collection-ID. Continue using the connection configuration supplied by your deployment rather than repointing it to the SDK server.

The legacy implementation lives in zeroset-inc/nebula. Discover the connected service's advertised inputs and outputs with MCP tools/list. Those tool schemas are not the public v2 HTTP bodies.

Moving this hosted integration to the public v2 API requires an explicit adapter migration, including effort-only search, collection isolation, and matching advertised and executed contracts. Changes to this repository's SDK server do not migrate or qualify the legacy deployment.