Wiff vs Context Mode

A side-by-side look at the Wiff and Context Mode MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Wiff logoWiffCoding Agents · Local subprocess (stdio)Deterministic, resumable multi-agent Codex workflows, drivable from any MCP client.60GoodAuth: not declaredContext Mode logoContext ModeCoding Agents · Local subprocess (stdio)Context window optimization for AI coding agents. Sandboxes tool output (98% reduction), persists session memory, and enforces routing across 17 platforms via MCP + hooks.69GreatAuth: no auth required

Verdict: choose Wiff for coding agents work as a local process; choose Context Mode for coding agents as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Wiff logoChoose Wiff when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: WIFF_BACKEND.
  • You want tools like workflow_start, workflow_status, workflow_wait.
Explore Wiff

Context Mode logoChoose Context Mode when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like ctx_batch_execute, ctx_execute, ctx_execute_file.
Explore Context Mode

Feature & specification comparison

Rows where the two servers differ are marked.

SpecWiff logoWiffContext Mode logoContext Mode
CategoryCoding AgentsCoding Agents
Quality signal60/100 · Good69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsWIFF_BACKENDNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars531,923
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools510

Tools & capabilities

Wiff tools 5

  • workflow_startLaunch a deterministic JavaScript workflow in the background, or resume a previous run without repeating successful unchanged agent calls. User and project preferences are loaded from Wiff config. Always pass the caller's absolute working directory as cwd.
  • workflow_statusRead the latest persisted status, phase, counters, result, and artifact paths for a workflow run.
  • workflow_waitWait until a workflow changes state or the timeout elapses. Call repeatedly until the run is completed, failed, cancelled, or interrupted.
  • workflow_cancelInterrupt all live agents and mark a workflow run cancelled.
  • workflow_modelsList the models each agent backend (codex, claude, cursor, kimi) can run, with supported reasoning efforts. Backends that are unavailable on this machine report an error instead of models.

Context Mode tools 10

  • ctx_batch_executeRun multiple commands + search multiple queries in ONE call. Opt-in `concurrency: 1-8` for I/O-bound batches.
  • ctx_executeRun code in 12 languages. Only stdout enters context.
  • ctx_execute_fileProcess files in sandbox. Raw content never leaves.
  • ctx_indexChunk markdown into FTS5 with BM25 ranking.
  • ctx_searchQuery indexed content with multiple queries in one call.
  • ctx_fetch_and_indexFetch URL, chunk and index. Cache reuses content within TTL (default 24h, override per-call with `ttl: <ms>`). `ttl: 0` or `force: true` to bypass. Pass `requests: [{url, source}, ...]` + `concurrency: 1-8` for parallel multi-URL.
  • ctx_statsShow context savings, call counts, and session statistics.
  • ctx_doctorDiagnose installation: runtimes, hooks, FTS5, versions.
  • ctx_upgradeUpgrade to latest version from GitHub, rebuild, reconfigure hooks.
  • ctx_purgePermanently deletes all indexed content from the knowledge base.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Wiff

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wiff": {
      "command": "npx",
      "args": [
        "-y",
        "@xxxoooxoxo/wiff"
      ],
      "env": {
        "WIFF_BACKEND": "YOUR_WIFF_BACKEND_HERE"
      }
    }
  }
}

Context Mode

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "context-mode": {
      "command": "npx",
      "args": [
        "-y",
        "context-mode"
      ]
    }
  }
}

Frequently asked questions

Wiff is categorized under Coding Agents and uses a local stdio subprocess. Context Mode belongs to Coding Agents and uses a local stdio subprocess. Pick Wiff for coding agents work and Context Mode for coding agents.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Wiff has no declared pricing — check the project's own site. Context Mode is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add wiff and context-mode as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Wiff has a quality signal of 60/100 (Good) with 4 views, 0 installs and 5 GitHub stars. Context Mode has 69/100 (Great) with 2 views, 0 installs and 31,923 GitHub stars.