touch-grass
Related Servers
Alternatives to touch-grass
- AlicenseAqualityBmaintenanceAn MCP server that provides access to Cronometer nutrition data, enabling users to pull food logs, macro and micronutrient summaries, and biometric data into Claude or Cursor. It supports daily nutrition tracking and raw CSV exports by interfacing with the Cronometer web protocol.27160 PyPI19MIT
- AlicenseBqualityCmaintenanceEnables users to query Apple Health metrics, workouts, and trends from CSV files exported via the Health Auto Export app. It allows MCP clients to analyze health data such as heart rate, sleep stages, and activity levels directly from local iCloud Drive storage.321 npm1MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first MCP server that gives Claude Code web search, page reading, video transcription, and image analysis — without paid API keys. Runs SearXNG + whisper.cpp natively on Apple Silicon for zero-cost, low-latency research workflows.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the Ambient Weather REST API. Query your personal weather stations conversationally from Claude Code, Claude.ai, or any MCP-compatible client.1MIT
- AlicenseAqualityDmaintenanceMCP server bridging Claude Code to local llama.cpp. Run local LLMs alongside Claude for experimentation, testing, and cost-effective inference.1913 npm1MIT
- AlicenseAqualityDmaintenanceCamera-based presence detection MCP server for Claude Code. Uses your webcam to check if you're sitting at your computer, and can automatically keep Claude working when you step away.13MIT
- AlicenseNot gradedqualityAmaintenanceA local-first MCP server that helps Claude Code prioritize your work by searching across your tools like GitHub and Slack.7 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceA minimal Python MCP server that enables Claude Code to call local Ollama models (e.g., gemma3) as a tool, routing low-stakes work off the API and onto a homelab.-
TDQS
Scored across 4 tools
log_touch_grass, check_grass_conditions, and suggest_activity are clearly distinct in purpose, with check_grass_conditions returning conditions and suggest_activity providing a recommendation. The only mild overlap is between check_grass_conditions and get_stats, which both return streak and cached location/weather, though the live-vs-cached distinction is well documented.
All four tool names follow the same imperative verb + object pattern in snake_case: log_touch_grass, check_grass_conditions, suggest_activity, get_stats. The naming convention is consistent and predictable with no mixed styles or vague verbs.
Four tools is well-scoped for this small domain: record an outing, check conditions, get a suggestion, and review stats. Each tool earns its place without redundancy or bloat.
The core lifecycle is covered: logging an outing, reading stats, checking live conditions, and receiving a suggestion. The main gap is the deliberate lack of any undo/correction or reset mechanism, which could be a dead end if a log is made by mistake.