A powerful MCP server for sending emails via 126.com SMTP service. Perfect for AI assistants and automation workflows!
Lit Pigeon is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
Model Context Protocol server exposing Lit Pigeon email authoring + rendering as MCP tools.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @lit-pigeon/mcp-server
# 2 — ask your agent something
> Model Context Protocol server exposing Lit Pigeon email authoring + rendering as MCP tools.
Lit Pigeon is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Lit Pigeon as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add lit-pigeon-mcp -- npx -y @lit-pigeon/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List managed assets newest-first. Optional filters narrow by folder, tag, free-text search, or pagination.
Takes no parameters.
Return the metadata for one asset.
Takes no parameters.
Upsert an asset record. The
Takes no parameters.
Remove one asset metadata record by id. Does not touch the underlying file.
Takes no parameters.
List every folder path used across saved assets.
Takes no parameters.
List every saved brand kit (id, name, counts only — call get_brand_kit for full content).
Takes no parameters.
Return the full content of a brand kit by id.
Takes no parameters.
Upsert a brand kit. Pass the same
Takes no parameters.
Remove a brand kit by id.
Takes no parameters.
Create a new, empty PigeonDocument and return its id. Use this id with every subsequent tool call.
Takes no parameters.
Return the ids, names, and updatedAt of every document held by this server.
Takes no parameters.
Return the full JSON of a document by id.
Takes no parameters.
Run validateDocument(doc) on the stored document. Returns an array of {path, message} errors. Empty array = valid.
Takes no parameters.
Patch the document.metadata (name, previewText). Any field omitted is left unchanged.
Takes no parameters.
Update one attribute on body.attributes (width, backgroundColor, fontFamily, contentAlignment).
Takes no parameters.
Return the set of supported block types. Use the value in
Takes no parameters.
Fetch a Figma frame via the REST API, convert it into a PigeonDocument, and load it into the server. Returns the new documentId plus any conversion warnings. The Figma access token must be a personal-access token with file:read scope.
Takes no parameters.
Serialize the stored document to MJML markup. Returns the MJML string.
Takes no parameters.
Render the stored document to email-client-safe HTML (via MJML). Returns the HTML string plus any renderer errors as JSON: { html, errors }.
Takes no parameters.
Append a new row to the body. Specify either
Takes no parameters.
Append a new block (text, image, button, divider, spacer, social, html, hero, navbar) to a specific column.
Takes no parameters.
Patch a block\
Takes no parameters.
Remove a block from a column.
Takes no parameters.
List every available template — the 4 starters (welcome, newsletter, transactional, promo) plus any saved during this session.
Takes no parameters.
Load a template into the server\
Takes no parameters.
Snapshot a stored document as a reusable template. Provide a stable
Takes no parameters.
Remove a template by id. Starter templates can be deleted from this session\
Takes no parameters.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Lit Pigeon costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_assets | no tags | |
| get_asset | no tags | |
| save_asset | no tags | |
| delete_asset | no tags | |
| list_asset_folders | no tags | |
| list_brand_kits | no tags | |
| get_brand_kit | no tags | |
| save_brand_kit | no tags | |
| delete_brand_kit | no tags | |
| create_document | no tags | |
| list_documents | no tags | |
| get_document | no tags | |
| validate_document | no tags | |
| set_document_metadata | no tags | |
| set_body_attribute | no tags | |
| list_block_types | no tags | |
| import_figma_frame | untrusted-input | |
| render_to_mjml | no tags | |
| render_to_html | no tags | |
| add_row | no tags | |
| add_block | no tags | |
| update_block | no tags | |
| delete_block | no tags | |
| list_templates | no tags | |
| load_template | no tags | |
| save_template | no tags | |
| delete_template | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.2.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Lit Pigeon in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.