- Home
- MCP servers
- Promptopia
Promptopia
- typescript
2
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"lumile-promptopia-mcp": {
"command": "npx",
"args": [
"-y",
"@lumile/promptopia-mcp",
"--client",
"claude"
],
"env": {
"PROMPTS_DIR": "<YOUR_PROMPTS_DIR>"
}
}
}
}Promptopia MCP is a dedicated server for managing, organizing, and reusing prompt templates with automatic variable substitution and multi-message conversation support. It provides persistent storage, MCP protocol integration, and a scalable TypeScript foundation so you can reuse prompts across AI applications and workflows with confidence.
How to use
You connect to Promptopia MCP through your MCP-compatible client, such as Claude Desktop, and expose stored prompts as MCP resources. Create, browse, and manage single-content prompts and multi-message conversation templates. At runtime, variables wrapped in {{variable}} are substituted with actual values, enabling dynamic prompts for different contexts. If you already have a library of prompts, you can organize them by structure, version, and metadata, then reuse them across projects or workflows.
How to install
Prerequisites: Node.js and npm installed on your system. You should also have a compatible MCP client configured to connect to an MCP server.
# NPX installation (recommended client setup)
npx -y @lumile/promptopia-mcp --client claude
Option 2: Local installation and manual run. You will build the server locally and run it as a stdio MCP server.
# 1) Clone the repository (local setup)
# git clone <your-repo-url>
# 2) Install dependencies
npm install
# 3) Build the server
npm run build
# 4) Run the server via stdio configuration (example path to build output)
node /path/to/promptopia-mcp/build/index.js
Configuration and management tips
If you are using the NPX-based setup, you typically provide a prompts directory via environment settings so the MCP server can read and write prompt data. For example, set PROMPTS_DIR to your local prompts folder.
For a local build, ensure your client configuration points to the exact runtime command and entry file, and pass the same PROMPTS_DIR value to keep the prompt storage consistent across environments.
Troubleshooting and debugging
Because MCP servers communicate via stdio, debugging can be challenging. If you encounter startup issues, verify that the runtime command and arguments exactly match what your client expects, and confirm that the PROMPTS_DIR path is accessible with appropriate read/write permissions.
Notes on usage patterns
Use the variable substitution feature to dynamically tailor prompts for different users or contexts. Take advantage of multi-message templates to model complete conversations with explicit user and assistant roles, including support for mixed content types such as text and images.
Available tools
CreatePrompt
Add a new prompt template or multi-message conversation template with automatic variable detection and storage in the Promptopia MCP repository.
ListPrompts
Retrieve and browse all available prompts with metadata, or fetch a single prompt by ID.
UpdatePrompt
Modify an existing prompt or multi-message template, including metadata and content changes.
DeletePrompt
Remove a prompt or template from storage, with optional version handling.
ApplyVariables
Automatically substitute detected {{variable}} tokens with provided values during runtime.
ResolveMultiMessage
Handle and render multi-message conversation templates with role-based messages and mixed content types.