mcpbeat

Context Cloud MCP Server

io.github.abhinavala/context-cloud
answering

Context Cloud is answering right now. Last checked 13 min ago. 113 installs a week from npm.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 29 · avg 12 · +23% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
338 ms
Response time
average over 24h
113
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add context-cloud --transport http https://api.contextcloud.pro/mcp/protocol
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "context-cloud": {
      "url": "https://api.contextcloud.pro/mcp/protocol"
    }
  }
}
~/.codex/config.toml
[mcp_servers.context-cloud]
url = "https://api.contextcloud.pro/mcp/protocol"
.cursor/mcp.json
{
  "mcpServers": {
    "context-cloud": {
      "url": "https://api.contextcloud.pro/mcp/protocol"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "context-cloud": {
      "url": "https://api.contextcloud.pro/mcp/protocol"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://api.contextcloud.pro/mcp/protocol sse needs key 327 ms 13 min ago

Context Cloud — questions

Answers built from our own checks of this server.

Why is there no tool list for Context Cloud?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Context Cloud working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 338 ms. The bar chart above shows every period we have measured.
Is Context Cloud still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Context Cloud?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Context Cloud need an API key?
Yes. Every time we knock, Context Cloud answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Context Cloud?
It answers our handshake in 338 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Context Cloud?
The npm package @contextcloud/mcp-client was installed 113 times in the last week. Week over week that is +23%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.