Summary

Turns a finished agent run into something that reaches you.

The value is the same as any notification hook — you stop watching a terminal — but the two transports make it unusually flexible: stdio when the agent runs on your own machine, HTTP with a per-request bearer token when it runs somewhere else and several callers share one server. If you would rather not have the key sitting in a config file, use the prompt-string form.

What it is

A Python MCP server that exposes ActivitySmith's notification and live-activity tools, so an agent can raise an alert or update a running activity mid-task.

What you get

Notification and live-activity actions available to any MCP client
Two transports from the same package: stdio for local clients, or HTTP with `uv run mcp-activitysmith --server`
In HTTP mode the key is read from the Authorization header on each request, so one running server can serve different callers
A published container image, `ghcr.io/stumpyfr/mcp-activitysmith:latest`, for a stdio setup with no local Python
A VS Code config shape that prompts for the key as a password input instead of storing it in the file

Requirements

An ActivitySmith API key and Python 3.12+. Run `uv sync`, then launch with the key in `API_KEY` for stdio, or pass it as a bearer token for the HTTP transport.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary