Unfour
Sign in 中文

Product features

One local workspace for backend troubleshooting and operations

Follow an API request through SSH logs and database state to a verified fix. API, SSH, and Database share your project context; Flow runbooks preserve repeatable steps. MCP lets Codex and Cursor use the same approved resources.

Download Unfour View on GitHub

Capabilities along the investigation path

Use API, SSH, and Database independently or together. Flow is the fourth core module for reusable local runbooks; MCP connects these resources to your coding agent.

Requests

API Client

Send and organize HTTP requests, inspect complete responses, and bring request evidence into the rest of the investigation.

  • Collections, folders, and saved requests
  • Environments, scripts, and response history
  • OpenAPI collection exchange
  • Unfour / Postman Collection and Environment exchange
Explore API Client

Servers

SSH Terminal

Connect to servers, inspect runtime evidence, work with remote files, and reuse multi-step operational tasks.

  • Interactive SSH terminal
  • SFTP file browsing and transfers
  • Command history
  • Reusable multi-step SSH tasks
Explore SSH Terminal

Data

Database Explorer

Inspect schema and data, edit supported rows, and run SQL when an API symptom needs database evidence.

  • SQLite, PostgreSQL, and MySQL
  • Schema, table data, and supported row editing
  • openGauss and table structure/data export
  • SQL and Saved SQL execution context improvements
Explore Database Explorer

Runbooks

Flow

Keep repeated troubleshooting, service checks, and deployment tasks as user-defined local runbooks using the same workspace resources.

  • API, SSH Task, and Database steps
  • Condition and Wait Until
  • Canvas and run history
  • Local-only; no Cloud Sync
Explore Flow

AI-assisted

MCP Integration

Let Codex or Cursor use your saved API, SSH, and database resources to investigate and verify behavior. Flow tools manage and execute the same local runbooks.

  • Local stdio MCP server
  • Workspace-scoped tools
  • Policy and confirmation boundaries
  • Codex, Cursor, and compatible clients
Explore MCP Integration

Troubleshooting path

Follow the issue across the backend instead of rebuilding context

An API error is often only the first clue. Keep the request, server logs, and database state in the same workspace. Decide the fix, then re-run the checks. Flow runbooks save the repeated steps; they do not infer a root cause.

  1. 1. API request
  2. 2. SSH evidence
  3. 3. Database state
  4. 4. Verify fix
Read the API error debugging guide

Local-first boundary

The workspace stays on your desktop by default

Unfour is a desktop application. Connections, credentials, and workspace context remain local by default, while MCP tools operate through the capabilities and policies exposed by the local Unfour workspace.

Desktop application

Core troubleshooting runs from the Unfour application on your machine.

Local credentials

Saved credentials remain on the device by default and are resolved only for requested operations.

Workspace context

Projects, environments, connections, and tools stay organized around a local workspace. Exchange whole-workspace definitions to reduce repeated setup, or keep a password-encrypted local backup with optional saved credentials.

Approved MCP capabilities

AI agents use the tools Unfour exposes, subject to workspace policy and confirmation checks.

Read the local-first development guide

Investigate the whole backend chain with less context switching

Download the single Unfour desktop application, or inspect the open-source core on GitHub.

Download Unfour View on GitHub