The Cloud

io.github.tekalabsPublished by GitHub account tekalabsv1.0.2Updated Nov 14, 2026

Governed memory and workspace for any AI: tasks, calendar, mail and pages, with per-action consent.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote MCP server giving an AI a governed workspace memory for tasks, calendar, mail and pages, with per-action consent.

What you can do
  • Manage tasks and calendar items in a shared workspace.
  • Read and work with mail alongside the assistant's other context.
  • Create and edit pages as persistent workspace memory.
  • Keep context across sessions through governed memory, with consent requested for each action.
When to use it
Useful when you want an assistant to keep working memory of your tasks, calendar, mail and notes in one place, and you want to approve each action it takes rather than granting blanket access.
Requirements
A remote streamable HTTP endpoint at mcp.thecloud.so; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
The server reaches mail, calendar, tasks and pages, so the assistant can see and change personal and work data. Actions are described as requiring per-action consent, so review each approval prompt before granting it.

Installation

In SourceWeft

  1. Open The 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 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/io.github.tekalabs%2Fthe-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": {
    "the-cloud": {
      "type": "http",
      "url": "https://mcp.thecloud.so/mcp"
    }
  }
}

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

3
  1. v1.0.2LatestNov 4, 2026
  2. v1.0.1Oct 9, 2026
  3. v1.0.0Sep 27, 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.