dFlow

sh.dflowPublished by dflow.shOfficial publisherv1.0.0Updated Oct 24, 2026

Deploy apps, databases, and services in your dFlow workspace.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A remote MCP server that lets an assistant deploy apps, databases, and services in a dFlow workspace.

What you can do
dFlow connects an assistant to a dFlow workspace so it can deploy apps, databases, and services there. The manifest lists no individual tools, so the exact operations are not documented in the supplied material. It is a hosted remote endpoint reached over streamable HTTP rather than a local package.
When to use it
Consider it when you already use dFlow and want an assistant to help deploy apps, databases, or services in your workspace without leaving the conversation. It is not useful if you do not have a dFlow workspace.
Requirements
A remote endpoint at app.dflow.sh reached over streamable HTTP. Authentication is required via OAuth. No environment variables or headers are declared.
Before you install
Deploying apps, databases, and services changes your workspace and may create running resources that incur cost. Access is granted through OAuth, so review the scopes you authorize. The manifest lists no tools, so confirm what actions the server can take before connecting.

Installation

In SourceWeft

  1. Open dFlow 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/sh.dflow%2Fmcp/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": {
    "dflow": {
      "type": "http",
      "url": "https://app.dflow.sh/api/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

1
  1. v1.0.0LatestOct 12, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.