Overview
Workspace integration activity answers a simple admin question: is this workspace using Atlas through external access paths? It is for workspace owners, administrators, and customer-success teams who need to understand adoption of REST API and MCP access. It is not a developer trace, prompt log, security audit stream, or surveillance surface. Use it to answer:- Is the workspace using API or MCP access at all?
- Which surface is active: REST API, MCP, or both?
- When was the latest successful integration call?
- Which public route or MCP resource is most active?
- Is there enough usage to justify rollout, training, or renewal follow-up?
What admins can see
Workspace admins can see:- Total successful integration calls
- REST API calls
- MCP calls
- Top routes or resources
- Last-seen timestamps
What stays private
Atlas does not expose:- Request bodies
- Prompt text
- Raw metadata JSON
- IP addresses
- Session replay
- Private workspace notes
What counts as usage
Atlas counts successful integration calls only.
Failed authorization attempts, rejected requests, browser page views, and normal
public browsing do not count as API or MCP activity.
Last seen and top resources
last_seen_at is the newest successful API or MCP integration event for the
workspace.
top_resources shows the most-used routes or MCP resources by count. It is a
coarse adoption signal, not a transcript of what users asked or saw.