Clerk Chat MCP Server
Related Servers
Alternatives to Clerk Chat MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAutomatically analyzes and optimizes AI prompts by calculating clarity scores, detecting risks, asking clarifying questions, and adding domain-specific requirements to improve AI interaction quality.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides stateful prompt optimization using research-backed techniques like APE and OPRO, learning from historical performance data via a vector database. It enables users to automatically refine prompts, retrieve high-performing examples, and track performance analytics through iterative feedback.5-
- AlicenseAqualityBmaintenanceVoice Agent Factory for Vapi phone agents: vertical templates, self-testing agents, audio forensics, prompt versioning, CI regression gates.611 npmMIT

promptlintofficial
AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to automatically lint and auto-fix their generated prompts before running them, helping improve prompt quality, security, and cost efficiency.1MIT- AlicenseAqualityAmaintenanceProvides coding agents with visibility into test health through tools for flaky test detection, test quality linting, and LLM evaluation harness, enabling them to triage failures, review test quality, and check prompt changes for regressions.9Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables a coding agent to iteratively rewrite a misbehaving prompt and rerun it, with every attempt graded against a frozen baseline by judges from other AI vendors so improvements are proven rather than assumed. It also classifies failures into nine origins, showing when the problem lies in the test set, rubric, judges, or surrounding code instead of the prompt.8Apache 2.0
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action: test cases, draft prompts, skills, tools, and improvement runs. There is no overlap between create/list/get functions for different entities.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_test_case, list_draft_prompts, get_tool). The naming convention is uniform and predictable.
The server has 10 tools, which falls well within the ideal 3-15 range. Each tool serves a clear purpose in the test management and prompt workflow, making the set well-scoped.
The core workflow of creating test cases, running tests, and saving results is covered, but there are gaps: no get/update/delete for test cases, and no update/delete for draft prompts. This limits full lifecycle management.