Skip to main content
Glama

Related Servers

Alternatives to org-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Notes, documents and tasks as plain Markdown on your own disk, for Windows and macOS. Your assistant files tasks with steps and dates, writes and edits documents passage by passage, and searches past work over local stdio, with no account or server; it never closes or deletes anything.
      40
      7
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with org-roam knowledge bases, allowing search, retrieval, creation, and linking of notes while respecting org-roam's file structure and conventions.
      15
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A privacy-first, local-first MCP server that provides 15 ADHD/second-brain tools for capturing, prioritizing, and resurfacing tasks with context from calendar, mail, and messages.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to capture and manage notes, tasks, events, and links in a private, file-first workspace, with tools for viewing today's agenda and searching Markdown notes.
      14 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Captures and retrieves Markdown records for a personal recording system, enabling journaling, input tracking, search, and date-range review.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to apply productivity-system presets such as GTD, Kanban, Scrum, PARA, and OKR by capturing, querying, updating, completing, and planning tasks with enforced workflows, stored locally in a SQLite file the user owns. It also provides deterministic completion and plan metrics plus an offline HTML report, with no cloud service, account, embedded LLM, or API key required.
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: capture creates, get_entry reads one entry, search/list_todos/agenda query in different ways, update_state/schedule/archive/add_note mutate different aspects. org_agenda and org_list_todos both surface open work but are differentiated by scheduled/due vs unscheduled, and descriptions explicitly call out the distinction.

    Naming Consistency4/5

    All tools use the org_ prefix with verb_noun naming (get_entry, capture, agenda, list_todos, search, update_state, archive_entry, schedule, add_note, read_file, list_files). Minor inconsistency: org_capture and org_agenda are noun/verb-less compared to the verb_noun pattern, but they are conventional org-mode terms and the pattern is otherwise consistent.

    Tool Count5/5

    11 tools is well-scoped for an org-mode server. Each tool covers a distinct operation needed to interact with org files: querying, capturing, editing state, scheduling, archiving, and file access. No redundant or excessive tools.

    Completeness4/5

    The surface covers the core org-mode workflows: capture, list/search/agenda views, state changes, scheduling, notes, archiving, and raw file access. Minor gaps: no tool to edit/rewrite headline text or delete entries outright, and no explicit tool to create a new file, but archiving and raw file read mitigate some of these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues