traktor-mcp
Related Servers
Alternatives to traktor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLocal STDIO MCP server for safely curating Spotify playlists with a plan/apply workflow, allowlist-based write protection, and authentication status checks.MIT
- AlicenseNot gradedqualityBmaintenanceSearch 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 PyPI7MIT

Daykeeper MCPofficial
AlicenseAqualityAmaintenanceA 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.824 npmApache 2.0- AlicenseAqualityCmaintenanceConnects 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.571 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects 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 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes 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
Scored across 4 tools
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.
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.
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.
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.