CloudArch Codeflow

ru.cloud-archPublished by cloud-arch.ruv0.1.1Updated Oct 24, 2026

Turn a TypeScript codebase into a live animated call-flow diagram on CloudArch.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Turns a TypeScript codebase into a live, animated call-flow diagram on the CloudArch service, driven from an AI assistant.

What you can do
  • Analyze a TypeScript codebase and derive its call flow.
  • Generate an animated call-flow diagram hosted on CloudArch.
  • Work with self-hosted CloudArch instances through an API base URL override.
  • No individual tools are listed in the manifest, so the exact operations are not documented.
When to use it
Useful when you want a visual, animated picture of how a TypeScript project's functions call each other, and you already use or are willing to sign up for CloudArch.
Requirements
Runs as a local stdio process, installed from the npm package @cloud-arch/mcp-codeflow, so Node.js is needed. Requires a CloudArch API key in the CLOUDARCH_API_KEY environment variable. The optional CLOUDARCH_API_URL variable points at a self-hosted instance instead of the default API. Desktop client only; network access to CloudArch is required.
Before you install
The API key is a secret sent to CloudArch; keep it out of shared configuration. Source code or derived call-flow data is likely uploaded to the CloudArch service, so check what leaves your machine before running it on private code. The manifest lists no tools, so review the package before installing.

Installation

In SourceWeft

  1. Open CloudArch Codeflow in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.