Skip to main content
Glama
irachrist1

daylens-mcp

by irachrist1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to daylens-mcp

No user-submitted related servers found.

    Related Servers

    • AI Memory MCP

      optimaquantum
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to semantically search your entire local conversation history from Claude Desktop, ChatGPT and Claude Code, and to retrieve, browse, ingest and report on those conversations. All embeddings run locally, so no cloud, API keys, or data leave your machine.
      MIT

    • coding-memory-mcp

      ChinaCarlos
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.
      18 npm
      2
      MIT

    • devrecall

      pavelpilyak
      A
      license
      A
      quality
      A
      maintenance
      Local-first dev memory: indexes Git commits, PRs, Jira/Linear tickets, Confluence docs, Slack threads, and Calendar events into a local SQLite/FTS5/ONNX index, and exposes them as MCP tools so Claude Code, Cursor, and Codex can search and cite your past work.
      17
      4
      MIT
    • Lien by getlien

      Lienofficial

      getlien
      A
      license
      Not graded
      quality
      A
      maintenance
      Lien connects AI coding assistants like Cursor and Claude Code to your codebase through the Model Context Protocol (MCP). Ask questions in natural language, get precise answers from semantic search—all running locally on your machine.
      2
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: timeline for daily blocks, focus stats for metrics, app usage for breakdown, search for querying history, and recent activity for up-to-the-minute info. No two tools clearly overlap.

    Naming Consistency4/5

    Four tools consistently use the get_ prefix (get_timeline, get_focus_stats, get_app_usage, get_recent_activity), but search_work breaks the pattern. While still readable, the inconsistency is mildly noticeable.

    Tool Count5/5

    Five tools is well-scoped for a personal analytics server, covering the main ways to access Daylens data without being bloated or sparse.

    Completeness5/5

    The set covers all the typical read-only needs for a work-tracking service: daily overview, metrics, detailed usage, search, and real-time activity. No obvious gaps for this domain.

    Resources