Skip to main content
Glama

Related Servers

Alternatives to obo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for tracking issues across multiple AI agent sessions, enabling agents to file, claim, complete, review, and close issues with a web UI for monitoring.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing Markdown-Driven Task Management (MDTM) files with task, parent task, environment, and workflow management, enabling structured development workflows.
      5 npm
      173
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local-first MCP server for retrieving a small evidence set and recording reviewed conclusions, policy-gated and redacted without giving an agent general filesystem access.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A configurable MCP server that enables creating custom analysis tools through JSON configuration, with built-in frameworks for error handling, self-evaluation, security guardrails, and output artifacts.
      7 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that establishes feedback-oriented development workflows with a Web UI and desktop app, allowing users to provide interactive feedback to AI models through prompts, images, and session tracking.
      -

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: create sessions, get/list items, list sessions, mark items complete/skip, find next item, get session status, and update item fields. The operations target specific resources and actions without overlap.

    Naming Consistency5/5

    All tools follow a consistent 'obo_verb' or 'obo_verb_noun' pattern (e.g., obo_create, obo_get_item, obo_list_sessions). The naming is uniform throughout, using snake_case and clear action descriptors.

    Tool Count5/5

    With 9 tools, the server is well-scoped for managing OBO sessions and items. Each tool serves a distinct function in the workflow, from creation to status tracking, without being excessive or insufficient for the domain.

    Completeness5/5

    The toolset provides complete CRUD/lifecycle coverage for OBO sessions and items: create sessions, list/get/update items, mark items as complete/skip, track status, and find next tasks. No obvious gaps exist for the stated purpose of session management.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive