Smart Prompts MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
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
Each tool has a clearly distinct purpose: help, list categories, search, get, create, check status, and compose. No overlap; descriptions clarify workflow order.
Most tools follow verb_noun snake_case (list_prompt_categories, search_prompts, get_prompt, etc.), but 'prompts_help' reverses to noun_verb, breaking the pattern.
7 tools is well-scoped for a prompt management server: discovery, retrieval, creation, composition, and status checking. Not too few or too many.
Covers discovery, retrieval, creation, and composition, but lacks update, delete, or list-all prompts, leaving notable gaps for full lifecycle management.