BuildFlow Enterprise Operations

io.github.jgaethle10Published by GitHub account jgaethle10v0.7.0Updated Oct 24, 2026

Discover, route, and hand off enterprise operations problems without exposing private records.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that helps an assistant discover, route, and hand off enterprise operations problems without exposing private records.

What you can do
BuildFlow Enterprise Operations is a remote, streamable HTTP MCP server hosted at base44.app. According to its registry description, it lets an assistant discover, route, and hand off enterprise operations problems while avoiding exposure of private records. No individual tools, parameters, or output formats are documented in the supplied material.
When to use it
Consider it when an assistant needs help triaging or routing enterprise operations issues and passing them to the right place. Because no tools are listed, verify the actual capabilities against your own requirements before relying on it.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the endpoint at base44.app. No packages, environment variables, or headers are declared, and no authentication is declared.
Before you install
The server is third-party hosted and no authentication is declared, so anything sent to it may be handled without an access control layer. The description mentions avoiding exposure of private records, but the input does not document how data is protected, stored, or shared. Do not send confidential operational data until you have confirmed the provider's handling practices.

Installation

In SourceWeft

  1. Open BuildFlow Enterprise Operations in the dashboard and add it to a workspace.
  2. 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.jgaethle10%2Fbuildflow/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.

{
  "mcpServers": {
    "buildflow-enterprise-operations": {
      "type": "http",
      "url": "https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.7.0LatestSep 25, 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 listedRequired15 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.