Smart Prompts MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time-to-live (5 minutes) | 300000 |
| GITHUB_PATH | No | Path within repo (optional) | |
| GITHUB_REPO | Yes | Repository name | prompts |
| GITHUB_OWNER | Yes | GitHub username or organization | jezweb |
| GITHUB_TOKEN | No | Personal access token (for private repos) | |
| GITHUB_BRANCH | No | Branch to fetch from | main |
| ENABLE_USAGE_TRACKING | No | Enable usage tracking | true |
| CACHE_REFRESH_INTERVAL | No | Refresh interval (1 minute) | 60000 |
| ENABLE_SEMANTIC_SEARCH | No | Enable semantic search | true |
| ENABLE_PROMPT_COMPOSITION | No | Enable prompt composition | true |
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 |
|---|---|
| prompts_helpA | Get help understanding how to use the Smart Prompts tools effectively. Returns guidance on tool usage, examples, and best practices. |
| search_promptsA | 🔍 ALWAYS START HERE: Search for prompts by keyword, category, or tags. Returns matching prompts with their metadata. This is the recommended first step before using get_prompt or creating new prompts. Helps avoid duplicates and find exactly what you need. |
| list_prompt_categoriesA | 📋 Overview: List all available prompt categories with prompt counts. Use this to explore the library structure and see what categories exist before searching or creating prompts. Great for discovering new areas. |
| get_promptA | 📖 Get Full Prompt: Retrieve a specific prompt by its exact name. ⚠️ IMPORTANT: Use search_prompts first to find the correct prompt name, then use this tool. Returns the complete prompt content with metadata and template variables. |
| create_github_promptA | ✨ Create New Prompt: Create a new prompt and save it directly to the GitHub repository. 🎯 WORKFLOW: Always use search_prompts first to check if a similar prompt already exists. Only create new prompts when needed to avoid duplicates. |
| compose_promptsA | 🔗 Combine Prompts: Combine multiple existing prompts into a single prompt. Perfect for creating complex multi-step workflows. 📋 WORKFLOW: Use search_prompts to find prompt names first, then compose them. |
| check_github_statusA | Check GitHub connection status and write access. Use this to verify GitHub operations are available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| compose_prompt | Compose multiple prompts together |
| search_prompts | Search for prompts by keyword |
| suggest_prompts | Get AI-powered prompt suggestions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Prompts | List all available prompts |
| Prompt Categories | List all prompt categories |
| Prompt Tags | List all prompt tags |
| Usage Statistics | Get prompt usage statistics |
| Recent Prompts | Get recently used prompts |
TDQS
Scored across 7 tools
Most tools have distinct purposes, such as check_github_status for GitHub connectivity, compose_prompts for combining prompts, and search_prompts for searching. However, get_prompt and search_prompts could be slightly confused since both retrieve prompts, but descriptions clarify that search_prompts is for discovery and get_prompt is for exact retrieval by name.
Tool names follow a consistent verb_noun pattern with snake_case throughout, like check_github_status and search_prompts. The only minor deviation is prompts_help, which uses a noun_verb structure, but it still fits the overall naming style and is readable.
With 7 tools, the count is well-scoped for a prompt management server. Each tool serves a clear role, from checking GitHub status to creating, searching, and managing prompts, without feeling bloated or insufficient for the domain.
The tool set covers core CRUD operations for prompts, including create_github_prompt, get_prompt, and search_prompts, with additional utilities like compose_prompts and list_prompt_categories. A minor gap is the lack of update or delete tools for prompts, but agents can work around this by creating new prompts as needed.