roxabi-sense
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@roxabi-sensewhat was I doing at 3pm?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
roxabi-sense
Workstation attention journal — light sensors, local store, agent surfaces.
Status: scaffold · design locked · implementation not started
Not screenpipe. Not a web SaaS. Not insideroxabi-factory.
Why
Screen capture + OCR is the wrong tool for “what was I doing?”.
You already have timestamped work in ~/.claude and ~/.grok. Meetings live in Claap. What is missing is a cheap focus spine: which app/window was active, which agent sessions were open, whether Slack/Discord was running — without pixels, keyloggers, or a 174 MB trial for 40 seconds of frames.
roxabi-sense is that spine. It publishes facts, not policy.
Related MCP server: Cortex
What it is / is not
Is | Is not |
Local user-session daemon (systemd | Factory hub module |
CLI + optional MCP + optional NATS publisher | Screen OCR / continuous screenshots |
Reads existing Claude/Grok session artifacts | Re-logs AI conversations |
Focus / idle / process presence | Meeting recorder (→ Claap) |
Edge sensor for Sentinelle later | Sentinelle decision brain (→ factory hub) |
Architecture (target)
collectors (facts only)
┌─────────────┐ ┌──────────────┐ ┌────────────────┐
│ focus/idle │ │ agent sessions│ │ process presence│
│ (Wayland / │ │ ~/.claude │ │ slack/discord │
│ AT-SPI) │ │ ~/.grok │ │ (running?) │
└──────┬──────┘ └──────┬───────┘ └───────┬────────┘
│ │ │
└────────────────┼───────────────────┘
▼
local store (SQLite)
~/.local/share/roxabi-sense/
│
┌───────────────┼────────────────┐
▼ ▼ ▼
CLI MCP NATS (opt-in)
day-slice agent query factory.event.host.*
status what_was_i… activity | stale onlyBoundary (ADR-091-aligned): sensors publish facts; roxabi-factory Sentinelle (hub module, not shipped yet) may consume host events and decide. This repo never opens Discord, never dispatches jobs, never applies ops policy.
Surface | Granularity | Depends on factory? |
Local store + CLI | Fine timeline | No |
MCP (stdio) | Query on demand | No |
NATS plane ① | Coarse heartbeats ( | Yes (bus up) |
Details: docs/ARCHITECTURE.md · purpose: docs/PURPOSE.md
Stack decision
Local daemon + CLI + MCP — not a Silex web boilerplate.
Candidate | Verdict |
| No — that shape is for client demos & product UI, not a user-session sensor |
Full stack inside | No — factory owns Sentinelle consumer; capture stays on the workstation |
Python 3.13 + | Yes — matches Roxabi satellites ( |
SQLite under | Yes — single-machine, Syncthing-friendly if paused |
MCP stdio | Yes — Claude / Grok / Hermes |
NATS publisher (optional extra) | Yes later — facts only, feature-flagged |
Tiny | Optional V2 — human glance only, not the product surface |
Setup model (target)
# 1. install
git clone git@github.com:Roxabi/roxabi-sense.git
cd roxabi-sense && uv sync
# 2. enable user service (writes unit under ~/.config/systemd/user/)
uv run sense install-service
systemctl --user enable --now roxabi-sense.service
# 3. human CLI
uv run sense status
uv run sense day --from 14:00 --to 16:00
# 4. agents (Claude Code / Grok) — MCP stdio
# mcpServers.sense.command = ["uv", "run", "--directory", ".../roxabi-sense", "sense", "mcp"]
# 5. optional NATS (when factory Sentinelle is ready)
# sense config set nats.enabled true
# sense config set nats.url nats://...No Podman required on the laptop for V1. M₂ may use the same user unit. M₁ host-sensor path (services snapshot only) is a later collector, not a Quadlet of this whole app.
Roadmap (coarse)
Phase | Deliverable |
0 — this scaffold | Public repo, purpose, architecture, empty package |
1 — local spine | Agent-session collector + store + CLI |
2 — focus | Wayland/COSMIC focus + idle (AT-SPI first) |
3 — MCP | 3–5 tools ( |
4 — NATS opt-in |
|
5 — optional | Process presence, filtered browser history, local status HTTP |
Out of scope forever (for this repo): OCR, continuous screenshots, keylogging, clipboard dumps, scraping Slack/Discord desktop clients, meeting transcription.
Relation to the rest of Roxabi
Project | Relation |
Future consumer (Sentinelle hub module). Not the home of collectors. ADR-091 | |
Downstream memory/insight may ingest sense observations later. Sense stays capture + query, not the entity graph. | |
Claap | Meetings — do not duplicate |
| Read-only sources for agent presence |
License
AGPL-3.0-or-later (same family as roxabi-cortex).
Status
Scaffold only — no collectors yet. Design intent is frozen enough to implement phase 1 without another product loop.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceA local-first AI secretary that gathers your work context into private memory and enables AI agents to search and summarize it over MCP.Last updated86MIT
- Alicense-qualityCmaintenanceProvides persistent memory to AI agents through a wearable device, storing notes, sessions, and activities in a local SQLite database accessible via MCP.Last updatedMIT
- Alicense-qualityCmaintenancePersistent activity journal for AI agents - enables logging and querying decisions, changes, errors, and observations across sessions.Last updated11MIT
- FlicenseAqualityCmaintenanceA local-first, privacy-first MCP server that passively indexes personal digital activity (screenshots, clipboard, notes, downloads, links) into a local database, enabling LLMs like Claude to access your context without cloud storage.Last updated4
Related MCP Connectors
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
TPermanent memory layer for AI agents. Mint moments to the Polygon blockchain via MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Roxabi/roxabi-sense'
If you have feedback or need assistance with the MCP directory API, please join our Discord server