Untangle

bio.untanglePublished by untangle.bioOfficial publisherv1.0.0Updated Oct 24, 2026

Bioprocess design: generate purification routes, simulate fermentation and separations, run TEA.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Untangle is a remote MCP server for bioprocess design, letting an assistant generate purification routes, simulate fermentation and separations, and run techno‑

What you can do
Generate purification routes for a bioprocess design task, as described in the registry entry, though no individual tools are listed in the manifest or README, so the exact operations are not documented here.
When to use it
When you are scoping a bioprocess and want an assistant to help draft purification routes, simulate fermentation and separation steps, or run techno-economic analysis, and you are willing to connect to a hosted service with OAuth sign-in.
Requirements
A remote MCP endpoint at mcp.untangle.bio over streamable HTTP; OAuth authentication is required, so you need an account with the provider. No environment variables, headers, or local packages are declared.
Before you install
OAuth sign-in grants the server access tied to your account; the manifest lists no tools, so review what data and actions are exposed after connecting. Design inputs may be sent to a third-party service, and any simulation or analysis output should be checked before use.

Installation

In SourceWeft

  1. Open Untangle 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/bio.untangle%2Funtangle/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": {
    "untangle": {
      "type": "http",
      "url": "https://mcp.untangle.bio/mcp"
    }
  }
}

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.0LatestSep 16, 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.