Skip to main content
Glama

Related Servers

Alternatives to konbu

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for CairnOS, a local-first productivity app. Exposes 13 tools that let Claude read and write the same local SQLite "brain" the app uses — create and update tasks, projects, reminders, ideas, and notes; classify natural-language brain dumps; and query overdue/today tasks and project context.
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Task and project management MCP server with OAuth for Claude Desktop, Cursor bridge, semantic search, staged write approval
      14 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      A local-first open-source MCP server that acts as a personal secretary, memory manager, and automation hub—it syncs Calendar, Gmail, Canvas, GitHub, and Health into a typed temporal memory graph, and enables approval-gated write actions like creating events, drafting/sending mail, and filing issues, all with telegram/slack/CLI interfaces and a SQLite-backed audit trail.
      33
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      A local-first MCP server that handles daily work tasks through your AI assistant: converts meeting notes into todos, manages todo lifecycle, tracks work hours, generates daily/weekly reports, organizes files via move-only operations, and diagnoses dev environments, all guarded by a human-maintained preview/apply safety model.
      25
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI agents to read, write, and organize notes in a local-first, human-in-the-loop note-taking app.
      4 npm
      2
      MIT

    TDQS

    A4.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource (event, memo, todo) and action (create, get, list, update, delete, mark done, reopen). The descriptions explicitly differentiate between resource types, eliminating any ambiguity.

    Naming Consistency4/5

    All tools follow a verb_noun pattern (e.g., create_event, delete_todo), but list operations use plural nouns (list_events, list_memos, list_todos) while other operations use singular, causing a minor inconsistency.

    Tool Count5/5

    With 18 tools covering CRUD for three resource types plus status transitions and a cross-resource search, the count is well-scoped and each tool serves a clear, necessary purpose.

    Completeness5/5

    The tool set provides full lifecycle management for events, memos, and todos (create, read, update, delete) plus status toggles and search. No obvious gaps exist for the planner domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues