Customization

MCP Activity History

Read back what your agents actually called through 1DevTool MCP after the fact — tool name, status, duration, project, terminal, error, and a safe input/output preview. The history survives app restarts, so a call you missed at 2pm is still there at 6pm.

MCP Activity History

More Screenshots

Click any image to zoom in

Settings → MCP → Activity listing recent browser tool calls with status, duration, project, and terminal
An expanded MCP activity entry showing the tool input and a truncated output preview for a browser snapshot

Why You Need This

How this feature boosts your daily productivity

Terminal badges tell you a tool fired, then they vanish — which is useless the moment you want to know why an agent's browser run went sideways ten minutes ago. Settings → MCP → Activity keeps up to 500 recent calls on disk with their status, duration, and the project and terminal they came from. Search by tool, project, terminal, or error text, filter to just the failures, expand a call to read its input and a truncated output preview, then copy the visible history or clear it. Large payloads are shortened and sensitive values redacted before anything reaches the interface, so the log stays readable and safe to share.

How It Works

Get started in 4 simple steps

1
1

Open Settings → MCP → Activity

The Activity tab lists recent 1DevTool MCP calls with tool name, status badge, duration, and the project and terminal each call came from.

2
2

Search or filter to what you need

Search by tool, project, terminal, or error text, and narrow the list with the status filter when you only want the failures.

3
3

Expand a call to see input and output

Each entry opens to show the arguments the agent sent and a truncated output preview, with sensitive values redacted and large payloads shortened.

4
4

Copy or clear the history

Copy visible exports what is on screen, Load older pulls further back through the retained entries, and Clear discards the stored activity.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# Something went wrong ten minutes ago
# The terminal badge already cleared
# Scroll the transcript looking for the call
# Guess which tool failed and why
# Restart the app and lose the trail entirely

The 1DevTool Way

Open Settings → MCP → Activity.
Filter to errors, expand the call.
Read the input and output preview — even after a restart.

Key Capabilities

Everything included with MCP Activity History

Review recent 1DevTool MCP calls after they finish, retained across app restarts
See tool name, status, duration, project, terminal, and error for every call
Search by tool, project, terminal, or error text
Filter to running, done, error, or interrupted calls
Expand a call to read its arguments and a truncated output preview
Copy the visible history, load older entries, or clear retained activity
Sensitive values are redacted and large binary results shortened before display

Why It Matters

The productivity impact of having customization built into your workspace

The Badge Is Not Enough

Terminal badges clear within seconds. Activity keeps the call so you can still answer "what did it actually do?" hours later.

Straight To The Failure

Filter by status and the errors surface on their own, with the message attached, instead of scrolling a transcript hunting for the moment it broke.

Survives Restarts

History is retained on disk, so quitting the app does not erase the evidence of the run you wanted to review.

Safe To Read And Share

Sensitive values are redacted and large payloads truncated for display, while the agent still receives the complete result.

Ready to boost your workflow?

Download 1DevTool for free and experience MCP Activity History along with 170 other features — all in one app.