Features / Activity & interfaces

See what ran. Find what needs attention.

Inspect routed tool activity and manage your servers through the Web UI, CLI, or macOS menu bar.

Why it matters

More intention.
Less guesswork.

When a tool call fails or returns something surprising, a chat transcript is only part of the story. Inspect the proxy’s activity and server state.

01

Activity log

Review recorded tool calls, their outcomes, and detected sensitive-data patterns.

02

Web UI

Manage your proxy from the embedded browser interface.

03

macOS tray

Get a quick look at server status and access management from the menu bar.

04

Command-line access

Inspect activity and server state from the terminal and scripts.

An example workflow

A surprising response. A place to investigate.

  1. Find the routed tool call in the activity log.
  2. Inspect its recorded outcome and available details.
  3. Check server state from the Web UI, terminal or macOS interface.

Where the boundary is

Visibility covers traffic routed through MCPProxy. Direct client connections and other agent actions are outside that record; recorded detail depends on configuration.

Explore the rest of your setup

Inside MCPProxy

Real screens. A setup you can see.

Actual local UI captures · September 11, 2026. Charts include demonstration traffic, not adoption metrics. Open either theme at full size.

macOS menu bar

A quick look.
Without switching windows.

Open MCPProxy from the menu bar to see recent calls, their intents, connected clients and the last 24 hours of activity.

Server controls, profiles and the full Web UI are right there when you need them.

Actual tray menu—not the main app window. Recorded local activity includes demonstration calls.

MCPProxy macOS tray menu showing a 24-hour histogram, recent calls with intents, client activity and server controls