Superpower

One MCP layer for browser AI and native desktop workflows.

English · 简体中文

Problem · Products · Why Superpower · Features · Platforms · Architecture · Quick start · Operation guide · Repository

Oxford × NUS collaboration
_{Practical MCP workflows across browser and desktop surfaces.}

Release status: v1.4.1 is the current public stable release. V1.5 is the active development line and adds review-first routing and workflow execution capabilities.

What problem does Superpower solve?

Web AI chats are good reasoning surfaces, but they normally cannot directly use your local files, command-line tools, private MCP servers, or desktop workflows. Superpower connects those two worlds: the web model can decide what tool work is needed, while MCP executes the requested action through a local or remote tool server and returns the result to the same conversation.

That makes Superpower useful when you want to keep working in ChatGPT, Gemini, Perplexity, Grok, Copilot, Qwen or another supported web chat while still using real MCP tools. It is not a replacement for coding agents such as Codex; instead, it provides a browser-first execution layer for users who prefer the web chat as the planning interface, want their own MCP stack, need a review step before execution, or want lightweight tool use without consuming a separate local-agent model quota.

In one line: use the AI chat you already have as the reasoning surface, and use MCP as the execution layer.

Products

Browser Extension Bring MCP tools directly into supported AI websites without leaving the conversation. Works inside ChatGPT, Gemini, Perplexity, Grok, Qwen and more Detects structured tool calls and returns results to the active chat Supports Streamable HTTP, SSE and WebSocket MCP connections Uses Streamable HTTP as the recommended local default for new setups Includes tool visibility, automation and review controls Install: Chrome Web Store Best for: browser-native AI workflows.

Desktop App Guide: Desktop usage and Quick Ask Use Superpower as a native MCP workspace outside the browser. Native Qt 6 Windows application Organizes Connections → Apps → Actions → Runs Provides a standalone MCP client, workflow review and guarded execution surface Distributed as a portable Windows package in GitHub Releases Best for: managing MCP connections and actions from one desktop workspace.

Why Superpower?

Superpower keeps tool execution close to the interface where the work happens. Use the browser extension when the conversation is the workspace, or use the desktop app when you want a dedicated MCP control surface.

Stay in context Use MCP capabilities without constantly switching tools or consoles.

Connect real tools Use local or remote MCP servers across browser and desktop workflows.

Keep control Choose exposed tools and review guarded actions before execution.

Features

• Shared MCP execution model across browser and desktop surfaces
• Browser-side tool discovery, structured call detection and result injection
• Native desktop workspace for connections, apps, actions and runs
• Local and remote MCP endpoints
• Review-first natural-language Action Router
• Dependency-aware Workflow Planner with explicit cross-step bindings
• Session-only Workflow Runner with one-step-at-a-time guarded execution
• Persistent controls and generated MCP instructions

Browser extension: connections, tools and automation controls.

Structured tool calls routed through MCP and returned to the workflow.

V1.5: review-first routing and workflows

The V1.5 development line maps natural-language intent to MCP capabilities, drafts schema-backed parameters, plans multi-step workflows, makes cross-step data bindings explicit, and keeps guarded execution reviewable. Workflow runs advance at most one MCP Action at a time; reviewed bindings and policy checks remain authoritative.

Supported platforms

The browser extension currently supports ChatGPT, Google Gemini, Perplexity, Google AI Studio, Grok, OpenRouter, DeepSeek, T3 Chat, GitHub Copilot, Mistral, Kimi, Qwen Chat, and Z.ai.

How it works

1. A browser or desktop workflow selects an MCP capability.
2. Superpower routes the structured request through the configured MCP connection.
3. The MCP server executes the tool.
4. The result is returned to the active browser conversation or desktop workflow.

Quick start

Browser Extension

1. Install Superpower from the Chrome Web Store.
2. Open the extension in Chrome and configure your MCP connection.
3. For the standard local proxy, use Streamable HTTP with http://localhost:3006/mcp.
4. Open a supported AI website and use Superpower from the browser workflow.

Connection compatibility: new local setups default to Streamable HTTP. Explicit legacy SSE endpoints such as http://localhost:3006/sse and WebSocket endpoints remain supported. Existing saved connection settings are not overwritten.

New to Superpower? Follow the Browser Extension Operation Guide for the full connect → inspect tools → review instructions → run a safe first task workflow. The same guide also explains how to test an unpacked local build without publishing it to the Chrome Web Store.

For manual or development installation, see docs/install/windows-extension.md.

Desktop App

1. Open the latest release.
2. Download Superpower-Desktop-*-Windows-x64.zip.
3. Extract the archive and launch the packaged desktop application.

Build the browser extension from source

Requirements: Node.js 22.12+, pnpm 9.x, and a Chromium-based browser.

git clone https://github.com/stloendays/Superpower.git
cd Superpower
pnpm install
pnpm base-build

Configure an MCP proxy, start it with your preferred transport, then load dist/ as an unpacked extension. For the exact reload-and-refresh loop used during development, see Test a local build without publishing.

Development

pnpm dev          # Development build
pnpm base-build   # Production build
pnpm type-check   # Type checking
pnpm lint         # Lint

Repository layout

The repository root is intentionally kept as an entry surface: standard project documents, workspace/build configuration, and the main product directories stay visible; implementation helpers and optional examples live under dedicated folders.

Superpower/
├── chrome-extension/          # Browser extension shell and background integration
├── desktop/                   # Native Qt desktop application and desktop examples
├── docs/                      # Documentation, install guides and README/site assets
├── packages/                  # Reusable TypeScript packages, including MCP Core/Host
├── pages/                     # Browser extension pages and content scripts
├── scripts/
│   ├── install/               # Windows source/release installer helpers
│   └── shell/                 # Build, environment and version shell utilities
├── README.md                  # Project homepage
├── README.zh-CN.md            # Simplified Chinese homepage
├── CHANGELOG.md
├── SECURITY.md
└── LICENSE

Security

Superpower executes user-configured MCP tools. Treat connected MCP servers and tool outputs as trusted only to the extent you trust their source and configuration.

• Review the MCP server configuration before connecting.
• Keep credentials out of public configuration files and issue reports.
• Prefer loopback-only local endpoints when remote access is unnecessary.
• Review guarded or state-changing actions before execution.

See SECURITY.md for the current security guidance.

Contributing

Issues and pull requests are welcome. Please keep changes scoped, document behavior changes, and include validation where practical.

Project discovery

Superpower is relevant to developers and researchers working with Model Context Protocol (MCP), AI agents, browser automation, Chrome extensions, agentic workflows, tool-using LLMs, local MCP servers, desktop AI workflows, Qt 6, and human-in-the-loop execution.

Useful search terms: MCP browser extension, Model Context Protocol Chrome extension, ChatGPT MCP tools, Gemini MCP, browser AI agent, agentic workflow, tool calling, MCP desktop client, MCP Streamable HTTP, human in the loop MCP.

License

Superpower is released under the MIT License.