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.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 12/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 32/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Nodiom Cloud。按照 https://mcp.popnx.com/i/synexiom-labs-nodiom-cloud.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(api.nodiom.md) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Nodiom Cloudhttps://api.nodiom.md/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsNodiom Cloud
用 Nodiom Cloud 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Nodiom Cloud,或回答中出现 Nodiom Cloud 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Nodiom Cloudhttps://api.nodiom.md/mcp开启新聊天,输入前先从插件列表中选择 Nodiom Cloud
用 Nodiom Cloud 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Nodiom Cloud,或回答中出现 Nodiom Cloud 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user nodiom-cloud https://api.nodiom.md/mcp应能看到 Nodiom Cloud 在列表中并显示已连接
用 Nodiom Cloud 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Nodiom Cloud,或回答中出现 Nodiom Cloud 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Nodiom Cloud 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Nodiom Cloud,或回答中出现 Nodiom Cloud 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Nodiom Cloud 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Nodiom Cloud,或回答中出现 Nodiom Cloud 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://api.nodiom.md/mcpJSON 设置在下方“开发者专用”中
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"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Synexiom-Labs 验证,该账户拥有此仓库
代码最后更新于28天前
使用 MIT
在 747 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 4 次检查中有 4 次响应 · 最近一次 747 ms · 检查于 2026年11月18日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/synexiom-labs-nodiom-cloud)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于28天前,最新版本(0.10.4)于32天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
| 本项 Nodiom Cloud | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 5/5 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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*).