Unfour

mcp
Security Audit
Warn
Health Warn
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Pass
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Local-first backend troubleshooting workspace for tracing failures across API, SSH, and databases, with MCP-assisted runtime evidence.

README.md

English · 简体中文

Unfour

A unified, local-first developer workspace for tracing backend failures from API requests through server logs and database state to verified fixes.

Unfour brings API testing, SSH, database tools, local Flow runbooks, and MCP-assisted troubleshooting into one desktop application.

License
CI
Release
Built with Tauri

Unfour overview

[!WARNING]
Windows NSIS installers are unsigned and may trigger SmartScreen or other
operating-system security warnings. Use SHA256SUMS.txt from the GitHub
Release to verify downloaded files.

Latest stable download ·
v0.14.0, released
2026-11-09 · Changelog ·
Release Notes

In preparation · v0.15.0 · Unreleased changes ·
Draft Release Notes

Download

Download the latest Unfour release
from GitHub Releases.

  • Windows is the primary distribution path: NSIS .exe installer. It is
    unsigned and may trigger SmartScreen.
  • macOS has Apple Silicon and Intel packages; real-device install/run
    verification was recorded for v0.9.0. They are not Apple-signed or notarized;
    Gatekeeper may block them.
  • Linux publishes an x86_64 (x64) AppImage only. It is Experimental and currently
    targets Ubuntu 22.04+. The v0.14.0 build used Ubuntu 22.04, with native
    runtime checks still open.
    .deb and .rpm packages are not formally supported or published.
  • Verify downloaded installers with the release SHA256SUMS.txt asset.

What Is Unfour?

Unfour helps backend developers investigate failures that span an API, a
server, and its database. Troubleshooting is Unfour's core product loop:
reproduce an issue with an API request, inspect server logs over SSH, check
database state, identify the cause, and make and verify a fix.

A unified, local-first workspace keeps requests, connections, local activity,
and layout together throughout the investigation. API testing, SSH terminals,
and database tools provide the capabilities for each step in that loop. Flow
combines those capabilities into local runbooks for repeatable checks and tasks.
Flow definitions are included in whole-Workspace import/export and the current
Pro Cloud Sync client. Execution and run history stay on the device. Flow is a
runbook for this workspace, not a general workflow platform.

MCP is an optional assisted layer: Codex and Cursor can use the local stdio
MCP server to work with the same saved API, SSH, database, and Flow data as
the desktop app. Its workspace-scoped tools run through the shared command
bus, subject to MCP policy and high-risk action confirmation checks.
MCP can save, run, cancel, and query Flows. It does not generate a
troubleshooting playbook, correlate requests with logs and database state, or
detect root causes. You author and start runbooks. Boundaries and confirmation
are in the MCP overview.

Unfour is one application and one product. Its core desktop features are free
and open source under Apache-2.0. An active Pro subscription unlocks Cloud Sync
in the same application. Pro is an entitlement within Unfour, not a separate
client, package, repository, or release.

The app is built with Tauri 2, React, TypeScript, and Rust. The frontend owns
the workbench UI, while security-sensitive execution such as HTTP, SSH,
database drivers, local storage, and credential references lives behind Rust
capability crates and the command bus.

Troubleshooting Workflow

API error
↓
Inspect server logs over SSH
↓
Check related database state
↓
Identify the cause
↓
Repeat the request and verify the fix

The investigation stays in one workspace, while you remain in control of each
request, SSH session, query, and verification step.

For Coding Agents

Codex or Cursor can use their own repository tools to inspect, change, and test
code. Unfour complements those tools with controlled access to API behavior,
SSH/server evidence, and database state through MCP, so the agent can help
investigate the running backend and re-check it after a change.

Unfour does not edit the repository itself: the coding client owns code changes,
while Unfour provides the runtime side of the investigation. You control the
workspace, environment, risky actions, and final decision.

Modules

  • API Client - Compose and send HTTP requests, organize saved requests into
    collections and folders, resolve shared workspace variables, inspect response
    body/headers/cookies/timing, run saved pre-request and post-response scripts,
    review script tests and console output, keep redacted history, and import or
    export collections and environments.
  • SSH Terminal - Manage SSH connections and terminal sessions (split panes,
    search, clipboard context menu, persistent redacted command history and
    typing suggestions, host-key trust, redacted logs), browse and
    transfer remote files over SFTP on ordinary SSH connections, and automate
    multi-step SSH tasks (command, upload, download) from the Connections /
    Files / Tasks sidebar.
  • Database - Manage database connections, browse schemas, run SQL with
    confirmation-aware safety checks (including multi-statement Run All /
    Run Selected), preview and edit table rows, review query output, and export
    table structure as SQL and data as SQL, CSV, or JSON.
  • Flow - Compose saved API requests, SSH tasks, and Database queries into
    local runbooks with Condition branches and Wait Until checks. Author them on
    the Canvas and inspect step results and run history. Definitions travel with
    a whole-Workspace import or export and the current Pro Cloud Sync client.
    Only definitions sync; run history and actual runtime inputs/outputs remain
    local. Detailed manual acceptance is tracked separately. See
    Flow V1.
  • Workspace - Scope saved requests, shared environments/variables,
    connections, activity, tabs, and layout state to a local workspace, with
    title-bar active-environment switching. Export/import whole Workspace
    definitions, including Flow definitions, or create a password-encrypted local
    backup with optional saved credentials. Import previews create independent
    copies. See
    Workspace exchange and backups.
  • MCP integration for Codex and Cursor - Expose local stdio tools through
    the same command bus used by the desktop app. Codex and Cursor can use the
    same saved API, SSH, and database connections to reproduce issues, inspect
    logs and database state, and verify a fix. They can also save, run, cancel,
    and query local Flows under the same safety checks. MCP does not generate a
    troubleshooting playbook. See the MCP overview.

Connect Codex and Cursor to Unfour MCP →

Encrypted backups are local files, separate from Pro Cloud Sync. A Workspace
export includes Flow definitions and omits run history. The current client syncs
Flow definitions with a 64 KiB payload limit, including input declarations and
ordinary defaults, but excludes actual runtime inputs/outputs, history and
credentials. Recognized sensitive/device-local material is rejected; arbitrary
secrets in free text cannot be reliably detected. Keep secrets in runtime secret
inputs or resource credential storage. Backups do not embed database or
private-key files. Review free-form scripts and SQL before sharing or syncing.

Cloud Sync refreshes saved data in already-open modules and the workspace
switcher after remote changes commit locally, while preserving drafts and
execution state. SSH Tasks support reviewed reruns and previous-parameter recall,
with shared English/Chinese feedback and retry for loading/refresh failures.
Database MCP calls bind policy and execution to one workspace per call; guarded
UPDATE/DELETE confirmation checks the parsed outer WHERE.

What's coming in v0.15.0

  • Windows bastion sessions. Open a temporary terminal from supported
    Xshell or SecureCRT launch arguments from JumpServer/QizhiTech AccessClient.
    On an idle, logged-in POSIX shell, explicitly select and confirm the
    terminal for command-only SSH Tasks or API requests through remote curl.
    Run the terminal curl capability check to enable faster transfers for eligible
    small requests. Bastion-specific SFTP/WinSCP, rz/ZMODEM and temporary-session
    Flow or K3s deployment are outside this release.
    Bastion setup and modes
  • SSH routes to private services. Select a saved jump host for API,
    Redis or network SQL. A live bastion can also serve as a window-local
    TCP route if its server permits forwarding.
    SSH routes
  • Redis and query results. Browse standalone Redis keys and TTLs in
    Database, opt into confirmed local writes, or use read-only checks in Flow
    and MCP. Page, select, copy and export returned SQL rows without rerunning
    the query. Redis setup
  • Resume work. If a saved API request was selected, restart into that
    request using its saved definition. Accept an SSH history suggestion and
    keep typing in the terminal. MCP masks secret environment variables in tool
    output.

Screenshots

Captured from Unfour 0.14.0 on Windows against the dedicated Demo Lab on
2026-11-09, at a native window size of 1920 × 1032. These are real execution
results with synthetic demo data, not mockups.

App overview — API collection and the three baseline orders

Unfour overview

API Client — order 1001 returned by the live Demo API

API Client

SSH Terminal — connected Lab session and SFTP sample files

SSH Terminal

This session uses the saved Lab root connection. It does not demonstrate
ordinary-account SFTP permissions or transfer acceptance.

Database — read-only role querying the same three baseline orders

Database

SSH Task — saved baseline check, completed with exit code 0

SSH Task

Flow — API health, SSH deployment, readiness, version, and database query

Successful Flow run

Local Development

Requirements:

  • Node.js and pnpm.
  • A stable Rust toolchain.
  • Tauri 2 prerequisites for your operating system.

Install and run:

pnpm install
pnpm tauri dev

pnpm install also installs Git hooks through lefthook. A commit formats staged
Rust files with cargo fmt and auto-fixes staged TypeScript with ESLint.
Skip once with LEFTHOOK=0 git commit.

Common commands:

pnpm tauri build        # create local Stable-channel Tauri bundles
pnpm tauri build:test   # create isolated Test-channel Tauri bundles
pnpm run build          # build the desktop frontend only
pnpm run check          # frontend build + Rust check + large-file check
pnpm run lint           # ESLint
pnpm run test           # frontend unit tests (Vitest)
pnpm run test:e2e       # Playwright smoke tests
pnpm run check:rust     # cargo check --workspace
pnpm run check:rust:ssh # cargo check with the ssh-native feature
pnpm run test:rust      # cargo test --workspace
pnpm run test:release-env # release/channel contract unit tests

Run commands from the repository root unless a package document says otherwise.
pnpm tauri dev defaults to the Test release channel, while local
pnpm tauri build defaults to Stable. Use pnpm tauri build:test for an
isolated Test-channel bundle. Set UNFOUR_STORAGE_PROFILE=dev when development
data should use ~/.unfour-dev; this storage override is independent from
release identity. Only CI should create formal publishable Stable artifacts,
with UNFOUR_RELEASE_CHANNEL=stable and an exact UNFOUR_BUILD_COMMIT.

Project Layout

Path Role
apps/desktop Tauri/Vite desktop app entry and Tauri adapter layer.
packages/app-shell Global shell composition and module mount slots.
packages/api-client API Client frontend module.
packages/ssh-terminal SSH Terminal frontend module.
packages/database Database frontend module.
packages/flow Local Flow runbook editor, Canvas, and run history.
packages/workspace-core Shared frontend workspace state.
packages/workspace-environments Workspace environments and variables management UI.
packages/workspace-local Local workspace lifecycle and whole-Workspace import/export UI.
packages/ui Shared UI primitives and stateless layout helpers.
packages/command-client Typed Tauri command wrappers and frontend command types.
crates/* Rust backend capability crates and adapters.

See docs/architecture/project-structure.md for the full package and crate
map.

Release Status

v0.14.0 is published. See the
v0.14.0 verification record
for distribution results and open native and live-service checks.
The release checklist
tracks the remaining v0.15.0 acceptance.

Documentation

Read the document that owns the question. The README stays usable on its own;
the links below are the detailed sources.

Question Document
How do I use the app? User guide
What can MCP do, and what must be confirmed? MCP overview
How do I connect Codex or Cursor? Client setup
What does a tool accept and return? MCP tools
How do I build the MCP server? Codex setup
What shipped, and what is only planned? Roadmap
Which release checks passed? Release verification
How is the repository split? Package boundaries, project structure
How are secrets and local data stored? Data storage, security model
How do Flow and Workspace exchange work? Flow V1, Workspace bundle

AGENTS.md and docs/agents/START_HERE.md are for coding agents working in
this repository. docs/release/release-checklist.md is the public release
checklist. docs/architecture/diagnostics.md covers local logs and diagnostic
bundles.

Contributing

Please read CONTRIBUTING.md, CODE_OF_CONDUCT.md, and the package boundary
rules in AGENTS.md before opening a pull request.

Security issues should be reported through SECURITY.md, not a public issue.

Support Unfour

If Unfour is useful to you, you can support its continued open-source development through GitHub Sponsors.

Sponsorship is optional and does not include Unfour Pro or paid cloud services.

Why Unfour?

The name “Unfour” is partly inspired by the Chinese idea of 四不像 — something that doesn’t quite fit into any single category.

Unfour isn’t just an API client, an SSH tool, a database client, or an agent workspace. It brings those usually separate capabilities together, so the name carries a bit of self-deprecating humor: it’s not quite any one of them, but has a little of each.

In traditional Chinese mythology, 四不像 is also associated with an auspicious mythical creature. That gave the name another meaning for me — a small hope that Unfour can grow into something a little unusual, but genuinely useful and built to last.

License

Licensed under the Apache License 2.0.

Reviews (0)

No results found