MCP Creator Growth
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DEBUG | No | Enable or disable debug mode for the MCP server. | false |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| learning_sessionB | Interactive quiz card. Call ONLY when user says 'quiz me' or 'test me'. Blocks until done. |
| debug_searchA | Search debug history for past solutions. AUTO-call silently on errors. |
| debug_recordC | Record debug solution. AUTO-call silently after fixing errors. |
| term_getC | Get unshown programming terms. Domains: programming_basics, algorithms, web_development, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| agent_guidelines | Get detailed agent behavior guidelines for using this MCP server. Use this prompt when you need comprehensive guidance on: - When to trigger learning_session - How to handle tool responses - Best practices for debug tools |
| quiz_template | Get a template for generating quiz questions about a topic. Args: topic: The topic to generate quiz questions about |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have mostly distinct purposes: debug_record and debug_search are both for debugging but focus on recording vs. searching, learning_session is for interactive quizzes, and term_get is for retrieving programming terms. There is some overlap between debug_record and debug_search in the debugging domain, but their descriptions clarify the difference, preventing significant confusion.
The naming is mixed: debug_record and debug_search follow a verb_noun pattern, but learning_session uses a noun-based name, and term_get uses a noun_verb pattern. This inconsistency makes the set less predictable, though the names are still readable and descriptive overall.
With 4 tools, the count is borderline for a 'Creator Growth' server, which suggests a broader scope. It feels slightly thin, as it covers debugging, learning, and terminology but lacks depth in areas like code creation or feedback tools that might be expected for growth-oriented purposes.
For a 'Creator Growth' domain, there are significant gaps: no tools for creating or editing code, providing feedback, tracking progress, or managing projects. The tools focus narrowly on debugging, quizzes, and terminology, leaving core growth workflows like iterative development or skill assessment uncovered.