Product features
Use the API Client, SSH Terminal, and Database Explorer yourself, or let an MCP-compatible coding agent use approved tools to gather and verify runtime evidence. MCP provides the controlled interface to those capabilities in your local workspace.
API, SSH, and database tools follow the same troubleshooting workflow. Each can be used on its own; together they keep request, server, and data evidence in one local workspace.
Requests
Send and organize HTTP requests, inspect complete responses, and bring request evidence into the rest of the investigation.
Servers
Connect to servers, inspect runtime evidence, work with remote files, and reuse multi-step operational tasks.
Data
Inspect schema and data, edit supported rows, and run SQL when an API symptom needs database evidence.
AI-assisted
Let a coding agent gather and verify runtime evidence with approved API, SSH, and database tools, alongside its own coding tools.
Troubleshooting path
An API error is often only the first clue. Unfour keeps the request, server evidence, and database state in one workspace so you can continue the investigation without opening a separate app. You still choose each request, session, and query.
Local-first boundary
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.
Core troubleshooting runs from the Unfour application on your machine.
Saved credentials remain on the device by default and are resolved only for requested operations.
Projects, environments, connections, and tools stay organized around a local workspace.
AI agents use the tools Unfour exposes, subject to workspace policy and confirmation checks.
Download the single Unfour desktop application, or inspect the open-source core on GitHub.
