Developer · Remote MCP server

Context Cloud

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

Visit Context Cloud's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.abhinavala/context-cloud
Version
0.1.8
Status
Active
Category
developer
Transport
SSE (HTTP + Server-Sent Events), stdio (local process)
Package
npm
Published
2026-05-22
Updated
2026-05-22
Publisher
abhinavala (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/abhinavala) · how
Website
contextcloud.pro
Repository
github.com/abhinavala/cntxtv2 (folder packages/mcp-client)
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
SSE (HTTP + Server-Sent Events)https://api.contextcloud.pro/mcp/protocolNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
SSE stream
Not opened: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npmruntime: npx@contextcloud/mcp-client0.1.8stdioNone declared

How to connect Context Cloud

Context Cloud is a remote MCP server reached over the older SSE transport, at https://api.contextcloud.pro/mcp/protocol. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @contextcloud/mcp-client version 0.1.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @contextcloud/mcp-client@0.1.8.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "context-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "@contextcloud/mcp-client@0.1.8"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
ContentrainGit-native content governance for AI agents - 27 deterministic MCP tools over stdio and HTTP.Remote & Local · HTTP, stdiostudio.contentrain.io
Contest MCPLog amateur-radio QSOs to N3FJP logging software over its TCP API.Local · stdioPyPI: contest-mcp
Context - ctxt.ioShare text, markdown, code, or HTML as auto-expiring links.Remote · HTTPLive check: ✓ handshakectxt.io
Context AutopilotMines your Claude Code and Cursor sessions into evidence-based CLAUDE.md / AGENTS.md rules.Local · stdionpm: context-autopilot
Context EngineCompress logs, retrieval chunks, and code context into structured LLM-ready signal.Local · stdioPyPI: melonelish-context-engine
Context FirewallLocal MCP proxy: collapses N servers' tools into 4 meta-tools and compresses large tool outputs.Local · stdionpm: context-firewall
Context FoundryRecursive Claude spawning for autonomous project builds with self-healing test loops.Local · stdioPyPI: context-foundry
Context ProxyMCP proxy that lazy-loads tool schemas to cut context token overhead by 6-7x.Local · stdionpm: mcp-lazy-proxy