{"_id":"@demomagic/mcp","name":"@demomagic/mcp","dist-tags":{"latest":"0.1.0"},"versions":{"0.1.0":{"name":"@demomagic/mcp","version":"0.1.0","mcpName":"ai.demomagic/interactive-video-guide","description":"DemoMagic MCP server — answers how-to questions about making interactive videos / AI product demos and points users to the right place to build one.","homepage":"https://demomagic.ai","author":{"name":"DemoMagic"},"type":"module","bin":{"demomagic-mcp":"dist/index.js"},"scripts":{"build":"tsc","start":"node dist/index.js","dev":"tsc --watch","inspect":"npx @modelcontextprotocol/inspector node dist/index.js","prepublishOnly":"npm run build"},"keywords":["mcp","model-context-protocol","demomagic","interactive-video","interactive-demo","ai-product-demo","loom-alternative"],"license":"MIT","dependencies":{"@modelcontextprotocol/sdk":"^1.29.0","zod":"^3.23.8"},"devDependencies":{"typescript":"^5.6.0","@types/node":"^22.0.0"},"_id":"@demomagic/mcp@0.1.0","gitHead":"f7a57cb0a59197ce3ce9ef96edb0567246ed70c7","_nodeVersion":"23.11.0","_npmVersion":"10.9.2","dist":{"integrity":"sha512-lmg3+orZ04CzGxR4FFHNqtmhmIvUJOOsqu7hLTX13nrYRZI6efrqvHVuhaLsQ1cLgp+KKFqvOWlq81wF1eHQpw==","shasum":"a2efb4fba6568440ac7d4a3ac6e94cce48874997","tarball":"https://registry.npmjs.org/@demomagic/mcp/-/mcp-0.1.0.tgz","fileCount":8,"unpackedSize":50731,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQDPqAjtfr93KQrB5U0/ADvw/VaRCWdCVTtCv7sI9Nf1mgIhAPIjPr3IygklDUmyZzNk49YSsKPopt8oCshPK0ZJLdBc"}]},"_npmUser":{"name":"demomagic","email":"luke@demomagic.ai"},"directories":{},"maintainers":[{"name":"demomagic","email":"luke@demomagic.ai"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/mcp_0.1.0_1781719447085_0.04699925457238052"},"_hasShrinkwrap":false}},"time":{"created":"2026-06-17T18:04:06.865Z","0.1.0":"2026-06-17T18:04:07.232Z","modified":"2026-06-17T18:04:07.439Z"},"maintainers":[{"name":"demomagic","email":"luke@demomagic.ai"}],"description":"DemoMagic MCP server — answers how-to questions about making interactive videos / AI product demos and points users to the right place to build one.","homepage":"https://demomagic.ai","keywords":["mcp","model-context-protocol","demomagic","interactive-video","interactive-demo","ai-product-demo","loom-alternative"],"author":{"name":"DemoMagic"},"license":"MIT","readme":"# DemoMagic MCP server\n\nA small, **read-only** MCP server that acts as DemoMagic's zero-CAC top-of-funnel inside AI assistants.\n\nWhen someone asks an AI client (Claude, Cursor, ChatGPT, etc.) a question like _\"how do I create a Loom that's interactive?\"_, _\"can I do AI product demos?\"_, or _\"how do I make a video that answers questions?\"_, the assistant calls a DemoMagic tool, gets genuinely useful how-to guidance, and is pointed to the right [demomagic.ai](https://demomagic.ai) landing page to actually build one.\n\nIt **does not** create, host, or share demos — that all happens on the site, behind the wizard each landing page shepherds the user into. This server is informational only.\n\n## What's inside\n\n- **15 use-case tools**, one per landing page, each with keyword-rich descriptions so the AI picks the right one and routes to the matching page:\n  `demomagic_loom_alternative`, `demomagic_interactive_demo_alternative`, `demomagic_screen_recorder`, `demomagic_record_a_bug`, `demomagic_how_to_videos`, `demomagic_sales_demos`, `demomagic_for_founders`, `demomagic_onboarding`, `demomagic_support_help_center`, `demomagic_product_tour`, `demomagic_pitch_deck`, `demomagic_course_creators`, `demomagic_employee_training`, `demomagic_interactive_presentations`, `demomagic_agencies`.\n- **1 general/overview tool** — `demomagic_interactive_video_guide` — for broad questions or when no specific tool fits.\n- **2 \"coming soon\" preview tools** — `demomagic_create_demo` and `demomagic_create_demo_from_video` — these advertise the roadmap (creating a demo from your assistant). They are **not functional yet**: they return a clear \"coming soon\" notice and route the user to build one on the site.\n- **Brand icon** on the server (MCP `2025-11-25` `icons` metadata, served from the deployed logo at `demomagic.ai/demo_magic_logo_1024.png`), plus a `demomagic://brand` resource exposing the logo/icon URLs.\n\nEach tool returns: the use-case headline, how it works (record **or** upload), why it works, an optional comparison, FAQ, and a **\"Create yours →\" link** to the relevant page.\n\nAll tool content lives in `src/content.ts`, mirroring the DemoMagic landing pages. Update it there when the pages change.\n\n## Develop\n\n```bash\nnpm install\nnpm run build      # compile TypeScript -> dist/\nnpm run inspect    # open the MCP Inspector against the server\n```\n\nQuick stdio smoke test:\n\n```bash\nprintf '%s\\n' \\\n'{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2025-11-25\",\"capabilities\":{},\"clientInfo\":{\"name\":\"smoke\",\"version\":\"0.0.0\"}}}' \\\n'{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}' \\\n'{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/list\",\"params\":{}}' \\\n| node dist/index.js\n```\n\n## Install in a client (local / stdio)\n\nAfter `npm run build`, point your MCP client at the built entry. Example (`mcp.json` / Claude Desktop / Cursor):\n\n```json\n{\n  \"mcpServers\": {\n    \"demomagic\": {\n      \"command\": \"node\",\n      \"args\": [\"/absolute/path/to/demo-ai-mcp/dist/index.js\"]\n    }\n  }\n}\n```\n\n## Distribution — important context\n\nMCP tools are **not** ambiently discovered by every LLM. An AI only sees this server if the user has **installed/connected it**. So discovery is two jobs:\n\n1. **Get installed** — publish to the MCP registries (**Smithery, MCPT, Open Tools**, + the official registry), and promote it yourself (an \"Add to Claude / Cursor\" button on the site, mentions in content). The keyword-rich tool names/descriptions also help registry search match user intent.\n2. **Get invoked once installed** — handled by the per-use-case tool design here.\n\nThis server is therefore a **registry + owned-promotion** channel into the AI-native builder/founder audience. To be discovered by people who've installed nothing (e.g. asking ChatGPT/Perplexity directly), pair it with **answer-engine optimization** of the landing pages themselves.\n\n## Publish to the official MCP Registry\n\n`server.json` is included and validated against the official schema (`2025-12-11`). Server name: **`ai.demomagic/interactive-video-guide`** (matches `mcpName` in `package.json`). Steps:\n\n1. **Publish the npm package first** (the registry verifies the package's `mcpName` matches `server.json`):\n   ```bash\n   npm publish --access public\n   ```\n2. **Install the publisher CLI** ([docs](https://modelcontextprotocol.io/registry/quickstart)):\n   ```bash\n   brew install mcp-publisher   # or download from the registry releases\n   ```\n3. **Verify the namespace.** We use the branded **domain** namespace `ai.demomagic` (published under DemoMagic, not a personal account), verified via a DNS TXT record on `demomagic.ai`:\n   ```bash\n   mcp-publisher login dns --domain demomagic.ai\n   ```\n4. **Publish the metadata:**\n   ```bash\n   mcp-publisher publish\n   ```\n\nThen submit/observe the same package on the other registries from the video — **Smithery, MCPT, Open Tools** — which index npm-published MCP servers.\n\n## Not yet built\n\n- Optional hosted **streamable-HTTP** transport at `mcp.demomagic.ai` (Cloud Run) for remote clients (add a `remotes` entry to `server.json`).\n- Per-tool icons once the SDK's `registerTool` helper exposes the `icons` field (currently the server `Implementation` icon + the registry `server.json` icon are wired; the spec also supports tool-level icons).\n","readmeFilename":"README.md","_rev":"1-947339316b3d53a08ca620d1e831295a"}