MJML MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging (set to 1 to enable) | 0 |
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 |
|---|---|
| compile_mjmlC | Compile MJML to HTML with various options |
| validate_mjmlB | Validate MJML syntax and structure |
| generate_templateC | Generate pre-built email templates |
| get_component_infoC | Get MJML component reference and documentation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: compiling MJML to HTML, generating email templates, retrieving component documentation, and validating MJML syntax. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task without confusion.
All tool names follow a consistent verb_noun pattern (e.g., compile_mjml, generate_template, get_component_info, validate_mjml). The naming is uniform and predictable, using snake_case throughout with clear action-object pairs.
With 4 tools, this server is well-scoped for its MJML-focused purpose. Each tool earns its place by covering essential aspects: compilation, template generation, documentation access, and validation, without being overly sparse or bloated.
The tool surface provides complete coverage for the MJML domain, including core operations like compilation and validation, as well as supporting features like template generation and documentation. There are no obvious gaps that would hinder an agent's workflow.