Skip to main content
Glama

Related Servers

Alternatives to traktor-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Search and read locally-recorded meeting transcripts over stdio. Read-only, no network. Exposes list_sessions, get_session, and search_transcripts to any MCP client.
      230 PyPI
      7
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A local stdio MCP adapter for the Daykeeper management API. It uses separately issued scoped credentials and exposes read-only tools by default; planning and mutations require explicit opt-in.
      8
      24 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Connects MCP clients to a self-hosted photo library through its REST API, exposing assets, albums, people, search, and optional administrative toolsets with read-only defaults and confirm-gated writes. It supports stdio and localhost Streamable HTTP transports.
      5
      71 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes an evidence-first Markdown store of current claims and tasks to AI agents over MCP stdio, letting them search, fetch, trace, list changes, validate, and run maintenance read-only by default. Dropping read-only mode additionally allows adding, transitioning, reviewing, and updating claims and tasks.
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation3/5

    status and plan are distinct read-only views, but purge and apply both mutate the collection with backups and Traktor-running guards, and plan already reports removals that purge handles. The boundaries are understandable from descriptions but not fully crisp.

    Naming Consistency3/5

    All names are single lowercase words, but the set mixes noun-like status/plan with verb-like purge/apply, so there is no predictable action pattern. It is readable but not systematic.

    Tool Count5/5

    Four tools map cleanly to inspect, preview, clean, and commit operations for a narrow collection-maintenance utility. No tool feels extraneous for the stated scope.

    Completeness4/5

    The surface covers the main lifecycle: status, plan, purge, and apply with backups. Minor gaps include no explicit post-apply verification or backup/restore management, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues