Sasha MCP reference

getTeamActivity

Who was active on this Sasha

Per-person activity on this Sasha for the last N hours (default 24): whether they signed in, chats started, messages sent, skill runs, MCP tool calls, documents written over MCP, app actions, agent runs, model tokens and cost in US dollars. actions is the sum of the counts except MCP tool calls: a skill, app or document call over MCP is also counted as a skill run, app action or document write, so mcpCalls overlaps those and is not part of actions; this tool's own calls are not counted. Sorted by actions; at most 50 people (truncated says if there are more). signedIn is a weak signal: a sign-in lasts 30 days, and members never sign in to the Sasha web interface, so judge activity by the counts. Admin only; the connection must ask for the usage:read-team scope by name.

Arguments

ArgumentTypeRequiredDescription
hoursintegeroptionalThe window, in hours back from now: 1 to 720. Default 24; 168 is one week.

Scopes

usage:read-team

Annotations

  • Read only: yes
  • Destructive: no

When to use

Call getTeamActivity when an admin asks who used Sasha, for example "who was active this week", or when a daily report needs a list of the active people. It counts what each person did in the last hours hours across the whole instance.

hours (optional) is the window, from 1 to 720. The default is 24; 168 is one week.

The result has windowHours, generatedAt (UTC), count (the number of people with any activity), truncated (true when count is more than the people listed) and users. users holds at most 50 people, the most active first, then by name. Each person has:

  • username: the sign-in name. On some instances it is an email address.
  • role: admin, staff or member.
  • signedIn: true when the person signed in to the Sasha web interface in the window. This is a weak signal. A sign-in lasts 30 days, and members never sign in to the web interface, so judge activity by the counts.
  • chats (chats started), messages (messages the person sent in chat), skillRuns (skills run through a connection), docWrites (documents created or changed through a connection), appRuns (app actions and app data changes) and agentRuns (agent runs the person started).
  • actions: the sum of those six counts. The list is sorted by it.
  • mcpCalls: tool calls from the person's Claude connections, not counting getTeamActivity itself. It is not part of actions, because it overlaps skillRuns, appRuns and docWrites: a skill, app or document call over a connection is counted in both.
  • tokens (model tokens in and out) and costUsd (model cost in US dollars, rounded to cents).

A person with no activity and no sign-in in the window is not listed. The result holds no email address other than a username, no id and no document name.

The tool needs the usage:read-team scope. An admin holds it. A staff user holds it only when an administrator has allowed it for them in Sasha. Members never hold it. It is never part of a default grant, and the chat in the Sasha web interface does not hold it: the connection must ask for it by name, for example a token minted for a daily report. An admin who connects or reconnects a client that asks for it sees it on the consent screen and can approve it there; an existing connection does not get it.

Example

{ "hours": 24 }

The result, made by running the tool on test data (generatedAt changes on every call):

{
  "windowHours": 24,
  "generatedAt": "2026-11-12T11:47:13.213Z",
  "count": 3,
  "truncated": false,
  "users": [
    {
      "username": "olivia",
      "role": "staff",
      "signedIn": false,
      "actions": 18,
      "chats": 3,
      "messages": 14,
      "skillRuns": 1,
      "mcpCalls": 0,
      "docWrites": 0,
      "appRuns": 0,
      "agentRuns": 0,
      "tokens": 237400,
      "costUsd": 4.19
    },
    {
      "username": "emma@example.com",
      "role": "admin",
      "signedIn": true,
      "actions": 5,
      "chats": 1,
      "messages": 4,
      "skillRuns": 0,
      "mcpCalls": 0,
      "docWrites": 0,
      "appRuns": 0,
      "agentRuns": 0,
      "tokens": 44800,
      "costUsd": 0.72
    },
    {
      "username": "sam@example.com",
      "role": "member",
      "signedIn": false,
      "actions": 2,
      "chats": 0,
      "messages": 0,
      "skillRuns": 0,
      "mcpCalls": 9,
      "docWrites": 2,
      "appRuns": 0,
      "agentRuns": 0,
      "tokens": 0,
      "costUsd": 0
    }
  ]
}

Refusals and what to do

  • If the connection does not hold usage:read-team, the tool is not in your tool list, and a call to it returns MCP error -32602: Tool getTeamActivity not found. A member can never hold the scope. A staff user needs an administrator to allow it first. A connection that did not ask for the scope by name does not have it: reconnect asking for usage:read-team, or mint a token that names it. Read the permissions section of getDocs.
  • hours outside 1 to 720, or not a whole number, is refused before the tool runs: MCP error -32602: Input validation error: Invalid arguments for tool getTeamActivity: ….
  • Error in getTeamActivity: internal:unexpected (request <id>): something failed inside Sasha. Quote the request id in suggestImprovement.

Related

  • getDocs has a team-activity section with the same rules, and a permissions section on scopes.
  • listSuggestions lists the improvement suggestions this connection sent.
Built with BernardCookie settings