tarana-mcp
Related Servers
Alternatives to tarana-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve read-only ISHARI shalawat content from Supabase, including verse translations, full chapters, audio recitations, reciters, and per-user bookmarks through MCP tools.-
- AlicenseAqualityCmaintenanceGives Claude read-mostly, row-level-security-aware access to a Supabase or plain Postgres database through tools for inspecting roles, listing and describing tables, selecting and counting rows with structured filters, plus opt-in read-only SQL and single-row inserts. Every call runs in a read-only transaction under the anon or authenticated role with JWT claims set, so RLS policies, schema allowlists, row caps and statement timeouts apply exactly as they would for a real client.5MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Supabase databases through standardized CRUD operations including querying, inserting, updating, and deleting records with support for filtering, pagination, and column selection.-
- AlicenseAqualityCmaintenanceEnables Claude and other MCP clients to list and query allowlisted Supabase tables, insert rows, and search, read, or create Notion pages. It ships with table allowlists, validated inputs, row limits, and an optional read-only mode that unregisters write tools, plus a mock mode for trying it without credentials.61MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform CRUD operations on Supabase databases through natural language. Supports advanced filtering, pagination, and safety checks for seamless database interaction.MIT
- FlicenseNot gradedqualityDmaintenanceConnects to a Gym Tracker Supabase database to provide LLMs with access to personal workout history, routines, and training progress. It enables users to analyze fitness performance, track personal records, and receive personalized coaching advice through natural language.-
TDQS
Scored across 8 tools
Most tools have clear resource/action boundaries (list/get for songs, setlists, and shows; band_stats is distinct). However, suggest_songs overlaps substantially with list_songs, since both filter songs by key and BPM range, and the distinction is only loosely clarified as 'for building a set.'
The set mostly follows a consistent snake_case verb_noun pattern: list_songs, get_song, list_setlists, get_setlist, list_shows, get_show, and suggest_songs. band_stats is the one deviation, using a noun phrase with no verb, but it is still readable and predictable.
Eight tools is well-scoped for a band repertoire/setlist/show assistant. Each tool covers a clear read-oriented operation, and there is no excessive surface area.
The read side is solid: songs, setlists, and shows all have list/get coverage, plus suggestions and stats. However, the surface has no create/update/delete operations for songs, setlists, or shows, and no way to edit setlists or booking status, which are notable gaps for a band management domain.