Context Cloud

io.github.abhinavalaPublished by GitHub account abhinavalav0.1.8Updated Oct 24, 2026

Persistent AI memory with shared team workspaces, typed knowledge chunks, and cross-tool support.

VerifiedSSEWeb executableKnowledge & Memory

Overview

AI-generated overview

Context Cloud gives an AI assistant persistent memory with shared team workspaces and typed knowledge chunks, usable across tools.

What you can do
  • Store and recall persistent memory across sessions.
  • Organize knowledge as typed chunks inside shared team workspaces.
  • Share the same memory context across different tools and clients.
  • Connect either through a hosted remote endpoint or a local npm client.
When to use it
Useful when you want an assistant to remember context between sessions, or when a team needs a shared, cross-tool knowledge store rather than per-chat memory.
Requirements
OAuth authentication is required. Runs as a remote SSE endpoint or as a local process via the npm package @contextcloud/mcp-client with npx, so Node.js is needed for the local option. No environment variables or headers are declared.
Before you install
Memory is stored in a third-party hosted service and shared across team workspaces, so anything the assistant saves may be visible to workspace members and leaves your machine. Review what gets written before relying on it for sensitive material.

Installation

In SourceWeft

  1. Open Context Cloud 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 SSE. 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/io.github.abhinavala%2Fcontext-cloud/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": {
    "context-cloud": {
      "type": "sse",
      "url": "https://api.contextcloud.pro/mcp/protocol"
    }
  }
}

README

This repository has no README.

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. v0.1.8LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.