Clerk Chat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLERK_CHAT_API_KEY | Yes | Clerk Chat API key for authentication | |
| CLERK_CHAT_API_BASE_URL | No | Base URL for the Clerk Chat API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_test_casesA | List all test cases in the database for a specific company |
| create_test_caseB | Create a new test case in the database for a specific company |
| run_testsA | Run regression tests against a system prompt with real LLM evaluation for a specific company. Use prompt_id (from save_draft_prompt) for faster performance, or system_prompt for direct text. |
| save_improvement_runA | Save a complete improvement cycle with prompts, analysis, and test results for a specific company |
| save_draft_promptA | Save a draft prompt to the database for a specific company for later use in testing. Returns a prompt_id that can be used with run_tests. |
| get_draft_promptA | Retrieve a previously saved draft prompt by ID for a specific company |
| list_draft_promptsB | List all saved draft prompts for a specific company |
| list_toolsA | List all available tools for a company. Use this when generating tests to know what tool calls are possible. |
| get_toolA | Get details of a specific tool by ID |
| list_skillsA | List all available skills |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| skill://prompt-improvement/feedback-analysis | |
| skill://prompt-improvement/improvement-loop | |
| skill://prompt-improvement/mcp-tools-guide | |
| skill://prompt-improvement/prompt-improvement | |
| skill://prompt-improvement/test-analysis | |
| skill://prompt-improvement/test-generation |
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.