Name: Activitysmith
Author: stumpyfr

LABSCO 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 — git clone https://github.com/stumpyfr/mcp-activitysmith

See installation options

USE CASES

01

Walking away from a long run

End the prompt with an instruction to notify you when the task finishes, and go do something else.

02

Watching progress on a multi-step job

Have the agent update a live activity as it moves between steps, rather than sending one notification at the end.

03

Running the server away from your laptop

Start it in HTTP mode and let each client pass its own key in the Authorization header.

BEFORE YOU INSTALL

What to know first

Requires

uv on PATH
Python 3.12+
API_KEY in your environment

Where it runs

Both documented clients run the server on your machine.

INSTALLATION

Connect your client

Server setup

Install

TERMINAL

git clone https://github.com/stumpyfr/mcp-activitysmith
cd mcp-activitysmith
uv sync

Run (HTTP)

TERMINAL

uv run mcp-activitysmith --server

MCP Clients

VS Code — HTTP

VS CODE — HTTP · JSON

{
  "servers": {
    "activitysmith": {
      "url": "http://127.0.0.1:8000",
      "headers": {
        "Authorization": "Bearer ${input:activitysmithApiKey}"
      }
    }
  },
  "inputs": [
    {
      "id": "activitysmithApiKey",
      "type": "promptString",
      "description": "ActivitySmith API key",
      "password": true
    }
  ]
}

Any MCP client — Docker

ANY MCP CLIENT — DOCKER · JSON

{
  "mcpServers": {
    "activitysmith": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "API_KEY=<YOUR_API_KEY>",
        "ghcr.io/stumpyfr/mcp-activitysmith:latest"
      ]
    }
  }
}

Activitysmith