Nexus Catalyst

com.nexus-catalystPublished by nexus-catalyst.comOfficial publisherv1.0.1Updated Oct 24, 2026

Cross-tool persistent memory and context for AI assistants over MCP.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Nexus Catalyst is a remote MCP server that gives an AI assistant cross-tool persistent memory and context.

What you can do
Provides persistent memory and context that carries across different tools used with the assistant, per the registry description. No individual tools are listed in the manifest, so the exact operations are not documented here. It is reached as a hosted remote endpoint rather than a local package.
When to use it
Consider it when you want an assistant to retain context between sessions or across multiple tools instead of starting fresh each time.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP, plus OAuth authentication, which the manifest marks as required. No environment variables, headers or local packages are declared.
Before you install
Because it stores persistent memory, information shared with the assistant may be retained across tools and sessions; treat sensitive data accordingly. Authentication is via OAuth, so review what access the provider requests. Tool behavior and data handling are not documented in the supplied material.

Installation

In SourceWeft

  1. Open Nexus Catalyst 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/com.nexus-catalyst%2Fnexus-catalyst/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": {
    "nexus-catalyst": {
      "type": "http",
      "url": "https://mcp.nexus-catalyst.com/"
    }
  }
}

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

1
  1. v1.0.1LatestSep 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.