SORNFlow

com.sornflowPublished by sornflow.comOfficial publisherv0.3.0Updated Oct 24, 2026

Document approval workspace. Remote MCP with OAuth; tools follow the signed-in member's space ACL.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A remote document approval workspace that lets an assistant work with documents according to the signed-in member's access permissions.

What you can do
SORNFlow is a remote MCP server for a document approval workspace. It connects over streamable HTTP and uses OAuth sign-in, and its tools operate within the space ACL of the signed-in member. No individual tools are listed in the available information.
When to use it
Consider it when an assistant needs to take part in document approval or review workflows inside SORNFlow, with access limited to what the signed-in member is allowed to see.
Requirements
A remote MCP endpoint at mcp.sornflow.com over streamable HTTP, plus an OAuth sign-in for a SORNFlow member account. No packages, environment variables, or headers are declared.
Before you install
The server relies on OAuth and enforces the signed-in member's space ACL, so the assistant acts with that member's permissions. Approval workflows may change document state. No tool list is published, so review the tools before granting access.

Installation

In SourceWeft

  1. Open SORNFlow 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/com.sornflow%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": {
    "sornflow": {
      "type": "http",
      "url": "https://mcp.sornflow.com/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. v0.3.0LatestSep 16, 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.