emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Review your AI agents' work in minutes, not hours of chat. Approve it or send it back.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 12/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 32/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Nodiom Cloud. Follow https://mcp.popnx.com/i/synexiom-labs-nodiom-cloud.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (api.nodiom.md) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Nodiom Cloudhttps://api.nodiom.md/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsNodiom Cloud
Use Nodiom Cloud and tell me what you can do for me, then show me one thing✓ If Claude says it is using Nodiom Cloud or shows a Nodiom Cloud tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Nodiom Cloudhttps://api.nodiom.md/mcpStart a new chat and pick Nodiom Cloud from your plugins before typing
Use Nodiom Cloud and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Nodiom Cloud or shows a Nodiom Cloud tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user nodiom-cloud https://api.nodiom.md/mcpYou should see Nodiom Cloud listed as connected
Use Nodiom Cloud and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Nodiom Cloud or shows a Nodiom Cloud tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Nodiom Cloud and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Nodiom Cloud or shows a Nodiom Cloud tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Nodiom Cloud and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Nodiom Cloud or shows a Nodiom Cloud tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://api.nodiom.md/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user nodiom-cloud https://api.nodiom.md/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nodiom-cloud": {
"url": "https://api.nodiom.md/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"nodiom-cloud": {
"type": "http",
"url": "https://api.nodiom.md/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account Synexiom-Labs, which owns the repo
Code last changed 28 days ago
Uses MIT
Responded in 747 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
The cloud address answered 4 of the last 4 checks · latest 747 ms · checked Nov 18, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/synexiom-labs-nodiom-cloud)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 28 days ago, and the latest version (0.10.4) reached the registry 32 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one Nodiom Cloud | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 5/5 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Structured reads and writes for Markdown.
Give AI agents a reliable way to work with the structure of your documents, without brittle string manipulation.
Nodiom reads and edits Markdown as a tree. Headings are branches; lists, paragraphs, tables and code blocks are nodes. You address them with path-like selectors, the way you'd query a DOM, and change one without rewriting, or breaking, the rest of the file.
| What it is | Where | |
|---|---|---|
| The library (this repo) | Structural read/write for Markdown in Node.js, on files or strings | npm install @synexiom-labs/nodiom |
| nodiom-mcp | An MCP server that gives AI agents these operations on your local Markdown files | Synexiom-Labs/nodiom-mcp |
| Nodiom Cloud | Hosted: shared state across agents and people. One board where AI agents hand in finished work and the people supervising them approve it or send it back | nodiom.md |
Structured state inside Markdown, here; shared state across agents and people, in Cloud. All three use the same engine and the same selectors.
When an AI agent, or any program, needs to change a Markdown document, it usually loads the whole file as a string, finds the right section with a regex, splices in new text, and hopes the formatting survived. Two writers at once, and one of them silently loses.
Nodiom treats Markdown as what it is: a tree. You say *where* (# Project > ## Tasks > li[contains="c_7f3a"]) and *what* (read, write, append, delete), and nothing outside that node changes.
import { Nodiom } from '@synexiom-labs/nodiom';
const doc = await Nodiom.fromFile('./project.md', { lock: true });
// Read everything under a heading (the heading line itself isn't included) const summary = doc.read('# Project > ## Summary');
// Add a task doc.append('# Project > ## Tasks', '- [ ] Deploy to staging');
// Tick it, addressed by its text rather than its position doc.write('# Project > ## Tasks > li[contains="Deploy to staging"]', '- [x] Deploy to staging');
// Remove the first finished item doc.delete('# Project > ## Done > li[0]');
// Write back to disk and release the lock await doc.save();
npm install @synexiom-labs/nodiom
Requirements: Node.js 18+
A selector is a " > "-separated path of segments, each matching a node in the document's structure.
"# Project Alpha" → The H1 "Project Alpha" and all its content
"## Tasks" → A top-level H2 named "Tasks" "# Project Alpha > ## Tasks" → The H2 "Tasks" nested under H1 "Project Alpha"
The number of # characters must match the heading's depth in the document.
Scope. "Content under ## Tasks" means everything after that heading until the next heading of the same or a higher level, which is how you'd read it.
Duplicate headings. If the same heading appears more than once in a scope, a bare segment is ambiguous and throws AmbiguousSelectorError; nodiom never silently picks the first. Qualify it with its parent heading, or address one by index, zero-based and negative-capable like li[n]:
"# Doc > ## Notes[0]" → The first "## Notes" under "# Doc"
"# Doc > ## Notes[1]" → The second "# Doc > ## Notes[-1]" → The last
The index must sit directly against the text. "## References [1]", with a space, is matched as a literal heading, and a heading that genuinely reads Tasks[1] is always tried literally first.
Frontmatter. A YAML (---) or TOML (+++) block at the top of a document is recognised as frontmatter. It never appears in tree(), can't be addressed by a selector, and is left byte-identical by every edit.
"## Tasks > li[0]" → First list item under ## Tasks
"## Tasks > li[-1]" → Last list item (negative indexing) "## Notes > p[0]" → First paragraph under ## Notes "## Arch > table[0]" → First table under ## Arch "## Arch > code[0]" → First code block under ## Arch
Element types: p, li, code, blockquote, table, hr.
An index is a position, not an identity. If another writer appends to the same section between the moment you compute li[2] and the moment you write to it, that index now points at a different node, and the write lands on the wrong one, silently.
Whenever more than one writer touches a document, address by content instead:
'## In Progress > li[contains="c_7f3a"]' → The list item whose text contains "c_7f3a"
"## Notes > p[contains='TODO']" → The paragraph containing "TODO"
The substring is matched against the node's own source text and must match exactly one node in scope. Matching several throws AmbiguousSelectorError rather than picking the first: silently editing one of several candidates is the failure this exists to prevent.
// From a file
const doc = await Nodiom.fromFile('./wiki.md');
// From a file, with an advisory lock (see Concurrency) const doc = await Nodiom.fromFile('./wiki.md', { lock: true, lockTimeout: 5000 });
// From a string: no filesystem, safe for serverless const doc = Nodiom.fromString(markdown);
// The Markdown under a selector. For a heading, its body without the heading
// line, so write(sel, read(sel)) changes nothing. const content: string = doc.read('# Project > ## Summary');
// Each list item's source under a selector, marker and nested lines included: // ['- [ ] Task A', '- [x] Task B\n - [x] sub-step'] const items: string[] = doc.readList('# Project > ## Tasks');
// Whether a location exists, and what it is const info = doc.query('# Project > ## Tasks'); // { exists: true, type: 'heading', depth: 2, childCount: 7, index: 3 }
// The heading outline const outline = doc.tree(); // [{ heading: 'Project', depth: 1, children: [{ heading: 'Tasks', depth: 2, children: [] }] }]
Mutations return this, so they chain.
// Replace the body of a section; the heading is kept
doc.write('# Project > ## Summary', 'On track for Q3.');
// Replace one list item. Text without its own bullet keeps the item's marker // and checkbox: this stays "- [ ] Final review (Friday)" doc.write('## Tasks > li[contains="Final review"]', 'Final review (Friday)');
// Add after the last node in a section, separated by a blank line doc.append('# Project > ## Tasks', '- [ ] Task C');
// Remove a node, or a heading together with its whole section doc.delete('# Project > ## Done > li[0]');
doc .append('# Project > ## Tasks', '- [ ] Task D') .delete('# Project > ## Done > li[-1]');
Your content is inserted as written (only trimmed), never re-serialized, and everything you didn't address is left byte-for-byte as it was.
const markdown: string = doc.toString();
await doc.save(); // write back to the original file, release any lock await doc.saveAs('./out.md'); // write to a new file (keeps the original lock) await doc.unlock(); // release the lock explicitly
import {
NodiomError, // base class of the errors below SelectorNotFoundError, // nothing matched; .suggestions has near misses SelectorParseError, // the selector itself is malformed AmbiguousSelectorError, // more than one node matched LockError, // couldn't get the file lock in time } from '@synexiom-labs/nodiom';
try { doc.read('# Project > ## Taks'); // typo } catch (e) { if (e instanceof SelectorNotFoundError) { console.log(e.selector); // "# Project > ## Taks" console.log(e.suggestions); // ["Tasks"] } }
A structural editor is only useful if it doesn't damage what it doesn't touch. Nodiom edits the source text at the node's exact position rather than re-printing the document, so formatting, spacing, list markers and escaping outside the edited node stay as they were. On a sample of 2,369 real-world Markdown files (an early user's own notes), every file round-trips byte-identically.
nodiom-mcp exposes these operations as MCP tools (nodiom_tree, nodiom_read, nodiom_read_list, nodiom_query, nodiom_write, nodiom_append, nodiom_delete) for Claude Code, Claude Desktop, Cursor or any MCP client, on Markdown files on your disk.
claude mcp add -s user nodiom -- npx -y @synexiom-labs/nodiom-mcp
When agents run on different machines, or come from different vendors, they need one place to share state. Nodiom Cloud is that place, built on this engine:
Connect from Claude, ChatGPT, Cursor or VS Code by adding one address and signing in, with no key to copy:
https://api.nodiom.md/mcp
There's a free plan. Setup for each app is at nodiom.md, and the full tool reference is in the docs.
On one machine, nodiom takes an advisory file lock via proper-lockfile. fromFile acquires the lock *before* reading, so two processes can't both read the old version and overwrite each other.
const doc = await Nodiom.fromFile('./shared-wiki.md', { lock: true });
// Other nodiom processes locking this file wait, or throw LockError after lockTimeout
doc.append('## Log', - ${new Date().toISOString()} Agent B finished the task); await doc.save(); // writes and releases the lock
The lock covers Node.js processes on the same machine. Across machines or serverless functions, use Nodiom Cloud, where every write runs under a database row lock on the document.
| Approach | Structured reads? | Structural writes? | Round-trip fidelity | Serverless | Concurrent |
|---|---|---|---|---|---|
fs.readFile + regex | No | Fragile | Depends on the regex | No | No |
gray-matter | Frontmatter only | Frontmatter only | Yes | Yes | No |
| Databases | No | No | No (loses the Markdown) | Yes | Yes |
| Vector DBs | Semantic only | No | No | Yes | Yes |
| nodiom | Yes | Yes | Yes | Yes (fromString) | Same machine |
| Nodiom Cloud | Yes | Yes | Yes | Yes | Across machines |
Planned, in no fixed order:
insert() with positional control: before or after a sibling node.diff(): a structural diff between two versions of a document.## *Tasks*).