dead-letter
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_emlA | Convert a .eml email file to Markdown with YAML front matter. Returns the full Markdown content (front matter + body). When output_path is provided, also writes the file to disk. Presets bundle common flag combinations:
Individual flags override the preset when provided. |
| convert_eml_to_bundleB | Convert a .eml file to a self-contained bundle with markdown and attachments. Creates a directory containing the converted markdown, extracted attachments, and optionally the original .eml source. source_handling only accepts 'copy' over MCP: the original .eml is copied into the bundle and left untouched. The 'move' and 'delete' modes are rejected here — use the CLI or the Python API for those. Returns JSON with bundle_path, markdown_path, attachment_paths, and optional diagnostics. |
| convert_directoryA | Batch convert all .eml files in a directory to Markdown. Recursively finds all .eml files and converts them. Returns a JSON summary with total, successes, failures, output_paths, and errors. Use convert_eml to retrieve individual converted file content. |
| get_diagnosticsA | Inspect email quality and structure without writing permanent files. Use this to assess conversion quality before committing, or to troubleshoot problematic .eml files. Always returns JSON with: state (normal/degraded/review_recommended), selected_body, segmentation_path, client_hint, confidence, fallback_used, and warnings. Two keys are conditional: stripped_images appears only when images were removed, and attachments only when the message had attachments eligible for retention. |
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
The tools are mostly distinct: single-file conversion, bundle conversion, batch directory conversion, and diagnostics each target a different workflow. convert_eml and convert_eml_to_bundle could be confused at a glance, but their descriptions clearly separate the content-only path from the attachment-inclusive bundle path.
Three tools follow the convert_* naming pattern, and get_diagnostics is a reasonable verb_noun deviation that still fits the overall style. The names are predictable and readable, with only the extra '_to_bundle' modifier creating a slight inconsistency.
Four tools is well-scoped for an email conversion server: single conversion, bundle conversion, batch conversion, and diagnostics. Each tool has a clear purpose and none feel redundant or excessive.
The server covers the core workflow of converting EML files to Markdown, including batch processing, attachment bundling, and pre-conversion diagnostics. Minor gaps exist—such as no direct batch-with-options or bundle-specific options—but the main workflows have no dead ends.