screentime-mcp-server
Related Servers
Alternatives to screentime-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables agents to query a local macOS archive of Knowledge and browser history through read-only stdio MCP tools for status, timelines, search, original records/blobs, schemas, bounded SQL, and usage or domain summaries.143MIT
- AlicenseAqualityCmaintenanceLets MCP clients search iMessages, read Apple Notes including checklist state, and look up Contacts on macOS.12MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools to read local Timing.app activity data, generate aggregated time entries, and push them to the Timing Web API.19 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to observe and operate macOS desktop apps, including existing browser windows and signed-in sessions, through a local MCP adapter.MIT
- AlicenseBqualityAmaintenanceEnables AI agents to directly access native macOS services, media, system health, and administration tools through a local MCP server.4020 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to read and search macOS Messages history through a read-only MCP interface.-
TDQS
Scored across 2 tools
get_screentime and screentime_sql have distinct roles: one is a convenience wrapper for date-specific usage, the other allows arbitrary SQL. However, an agent might be unsure when to use the specific date tool versus writing SQL, especially since both can return usage data.
The names follow different conventions: get_screentime uses a clear verb_noun pattern, while screentime_sql is noun-based and lacks a verb, making the set feel inconsistent. This mixing reduces predictability.
Two tools is quite thin for a server that could expose more granular Screen Time operations (e.g., date ranges, app lists, totals). The SQL escape hatch adds power, but the surface still feels minimal.
The combination of a targeted get_screentime tool and a general SQL query tool covers most retrieval needs, including custom queries. Minor gaps exist (e.g., no built-in date-range summary or app enumeration), but the SQL tool allows agents to compensate.