MDMagic Reviews and Details

Questions & Answers

1. What makes MDMagic unique?

   Custom Word templates. Drop your firm's .docx in once — letterhead, fonts, brand colours, headers, footers — and every conversion lands in that template. Markdown in, polished branded document out. Most converters give you their styling; MDMagic uses yours.

   The MCP server is the second wedge. Plug it into Claude Desktop, Claude Code, Cursor, OpenClaw, or VS Code and your AI assistant produces branded documents directly inside the chat. No copy-paste, no opening Word, no reformatting.

2. Why should a person choose MDMagic over its competitors?

   Three reasons.

   1. Custom Word template support is built in from the ground up. Most Markdown-to-Word tools give you their default styling; MDMagic applies yours — your letterhead, your fonts, your brand. The differentiator that earns the paying tier.

   2. MCP integration with every major AI assistant (Claude Desktop, Claude Code, Cursor, OpenClaw, VS Code). Your AI produces branded documents directly inside the chat. Most competitors aren't built for this workflow.

   3. Honest pricing. Free tier renews credits daily — no time-limited trial. Paid plans from $12/month. No watermarks, no feature gates between tiers. The only difference between Free, Starter, and Pro is volume.

3. How would you describe the primary audience of MDMagic?

   Anyone who has ever pasted AI output into Word and spent twenty minutes reformatting it by hand. That's a wide net by design — consultancies producing client deliverables, law firms drafting briefs, technical writers turning AI-assisted drafts into deliverable PDFs, agencies generating reports, software teams shipping styled documentation alongside their code, academics producing APA/MLA/Chicago-formatted papers.

   The common thread: Markdown is the source of truth in the user's workflow, the output needs to look like their company made it, and the manual reformatting step is the friction MDMagic removes.

4. What's the story behind MDMagic?

   MDMagic was built by Nexus IT Group, an Australian AI consultancy and software studio, as the practical fix for the "AI output looks generic" problem the team kept hitting in client work. Every AI tool produced beautifully-written Markdown that then needed 20 minutes of manual reformatting before it could be sent to anyone.

   Pandoc solved part of it — but Pandoc's setup is hostile to non-developers. So MDMagic was built as the layer on top: drag-and-drop template management in the web app, and an MCP server so AI assistants can drive conversions directly.

   Shipped April 2025. Spent 13 months operating quietly while the product was refined against real customer use. May 2026 is the first deliberate marketing push.

5. Which are the primary technologies used for building MDMagic?

   Node.js / TypeScript on the backend (Express 5). React + Vite on the frontend. Supabase Postgres for auth and persistence. Stripe for billing. Microsoft Graph API for native PDF rendering. The MCP server is published on npm as @mdmagic/mcp-server (MIT licensed, open source on GitHub) and supports both stdio and Streamable HTTP transports.

   The conversion pipeline is built around Pandoc with custom orchestration for template handling, plus Mammoth.js for high-quality HTML output.

6. Who are some of the biggest customers of MDMagic?

   We're in early-stage growth — customer permission is required before we list anyone publicly. Customer references available on request via team@mdmagic.ai.

Is MDMagic good?