Nebula

xyz.automatoncolonyPublished by automatoncolony.xyzOfficial publisherv0.3.0Updated Oct 24, 2026

Per-client memory for any AI. On a clash, the AI gets both values and is told to ask you.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Nebula is a remote, OAuth-protected memory service that gives an AI assistant per-client memory, surfacing conflicting stored values for the user to resolve.

What you can do
  • Store and recall memory that is kept per client, so an assistant can carry context across sessions.
  • When two stored values clash, return both values to the assistant and prompt it to ask the user which one applies.
  • No tool list is published, so the exact set of memory operations is not documented in the supplied material.
When to use it
Worth considering when you want an assistant to remember information about you or a client between conversations and to flag contradictions rather than silently pick one value.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address; OAuth authentication is required. No environment variables, headers or packages are declared.
Before you install
Memory content is stored with a third-party hosted service and sent to it over the network, so consider what personal or client information you let the assistant save. Access is granted through OAuth, so review the scopes requested during sign-in.

Installation

In SourceWeft

  1. Open Nebula in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.automatoncolony%2Fnebula/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nebula": {
      "type": "http",
      "url": "https://nebula.automatoncolony.xyz/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.3.0LatestOct 12, 2026
  2. v0.2.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.