Tofu

ai.trytofuPublished by trytofu.aiOfficial publisherv1.0.58Updated Oct 29, 2026

Deploy an app and keep it running: status, logs, versions, domains, databases and sign-in.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Tofu is a remote MCP server that lets an assistant deploy an app and manage it afterwards: status, logs, versions, domains, databases and sign-in.

What you can do
  • Deploy an app and keep it running from the assistant.
  • Check deployment status and read logs.
  • Review and manage app versions.
  • Manage domains and databases attached to the app.
  • Handle sign-in for the deployed app.
When to use it
Useful when you want an assistant to ship an app to a hosting platform and then operate it — checking whether it is up, reading logs, rolling versions, wiring domains and databases — without switching to a separate dashboard.
Requirements
A remote MCP endpoint at app.trytofu.ai over streamable HTTP. OAuth authentication is required, so a Tofu account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server can deploy and change live apps, including versions, domains, databases and sign-in settings, so assistant actions may alter or take down running services. OAuth grants access to your Tofu account; review the scopes requested. App data and logs are handled by the third-party Tofu platform.

Installation

In SourceWeft

  1. Open Tofu 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/ai.trytofu%2Ftofu/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": {
    "tofu": {
      "type": "http",
      "url": "https://app.trytofu.ai/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.58LatestOct 29, 2026

Score

72% 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

    Publish an icon in the registry entry.

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