Skip to main content
Glama

Related Servers

Alternatives to bort

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables task management with persistent SQLite storage, along with tools, resources, subscriptions, prompts, and completions over stdio or Streamable HTTP with per-user authentication.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets an AI assistant search and read the meetings recorded by Recordist on your own computer: transcripts, action items and notes. Local stdio server that talks only to the app's loopback API or its SQLite file; nothing leaves the machine.
      482 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create and manage small project plans—including tasks, assignees, status, progress, dates, and dependencies—and retrieve Gantt-friendly project views over MCP stdio. State is stored in SQLite without external dependencies.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Exposes SQLite database query tools and markdown document resources over JSON-RPC 2.0 stdio transport, enabling AI assistants to read and search documents and execute read-only SQL queries.
      8
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables task management through natural language: create tasks, list and filter them, and update their status. It uses SQLite for persistence and supports both local stdio and remote SSE transports.
      13 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action, and the project/task/chat/person prefixes make boundaries clear. The only fuzziness is between bort_summary (cross-project aggregates) and bort_project_summary (single project), plus mild overlap with bort_project_get, which also returns money and tasks, but the descriptions distinguish scopes adequately.

    Naming Consistency4/5

    All tools share the bort_ prefix and follow a resource_action pattern (project_list, task_create, chat_attach, expense_add), which is highly predictable. The lone global bort_summary lacking a resource prefix is a minor deviation from an otherwise consistent convention.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range for a project-management server covering projects, tasks, chats, people, expenses, and summaries. Each tool earns its place without redundancy.

    Completeness3/5

    Core lifecycles (project create/update, task create/update/close, chat attach/detach/list, expense add) are covered, but there are notable gaps: no expense update/delete/list, no standalone person list/get, no project delete/archive, and tasks lack a standalone list or reopen. Agents can partly work around via bort_project_get, but the surface is not fully rounded.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues