[INTEGRATIONS · 29 GUIDES]
The same 6 KB snippet drops into any framework, site builder, CMS or store — then muro's AI answers from your own docs and hands off to you when it isn't sure. Pick your platform.
Drop the snippet in your layout or root — one line, no SDK, no build step.
You do not need an npm package or a React provider to add chat to Next.js. One script tag in the layout, around 6 KB, loaded async.
Read the guide →Two clean ways to install a live chat widget in a plain React SPA built with Vite or Create React App: a one-paste snippet in index.html, or a useEffect loader with an idempotency guard. Plus why the widget survives client-side route changes, and how to turn on grounded AI replies with human handoff.
Read the guide →Two ways to add live chat to a plain Vue 3 + Vite app: a one-line paste in index.html or an onMounted loader in App.vue. Includes the vue-router nuance that trips people up, and how to switch on grounded AI replies that hand off to a human when it matters.
Read the guide →Add live chat to Angular the simple way: one snippet in src/index.html loads the widget once across the whole SPA, with no component and no change-detection impact. Use environment.ts for per-environment widget IDs and point the AI at your docs.
Read the guide →Add a live chat widget to your Nuxt 3 app in minutes. Two clean, SSR-safe approaches: an inline loader under app.head.script in nuxt.config.ts, or a dedicated client plugin in plugins/. Full code, no hydration warnings.
Read the guide →A practical guide to adding live chat to a Remix or React Router v7 app. Install the muro widget in app/root.tsx with dangerouslySetInnerHTML, understand exactly what happens through hydration and client-side navigation, then point the AI at your docs so it answers the repetitive questions for you.
Read the guide →Add live chat to Gatsby the right way: inject the widget from gatsby-ssr.js with onRenderBody so it loads once, outside React, with no hydration warnings. Then point muro's AI at your MDX docs so most questions answer themselves.
Read the guide →Static-site generators are the easiest place to add live chat: they all give you one spot to inject head markup on every page. Here is the exact spot for each.
Read the guide →A Turbo-safe guide to adding live chat to Ruby on Rails. Where the snippet goes in application.html.erb, why Turbo Drive does not break it, how to keep chat out of your admin layout, and how to turn on AI replies grounded in your docs.
Read the guide →Add live chat to a Laravel app with one edit to your Blade layout, keep it off admin routes with a simple @if, and use Blade stacks if you like things tidy. Then point muro's AI at your docs so most questions answer themselves, with reply-by-email for the rest.
Read the guide →Add live chat to a Django app with one edit to templates/base.html: no Channels, no ASGI migration, no Redis. The admin stays clean because it never extends your base template, and a tiny context processor keeps the widget off staging. Then point muro's AI at your docs so most questions answer themselves.
Read the guide →Paste one embed into the site-wide head — no developer needed.
Adding live chat to Webflow takes about ten minutes, but most guides skip the part where site-wide custom code requires a paid site plan. Here is the honest install path, the free Embed element workaround, and how to train the AI on your docs so most questions never reach you.
Read the guide →Adding live chat to a Framer site takes one script and the built-in Custom Code field. Paste it into Settings, General, Custom Code, publish, and test in the live preview. Then point the AI at your docs so the chat actually answers questions on day one.
Read the guide →A practical guide to adding a live chat widget to your Wix site with muro. It covers where the custom code setting lives, the Premium plan requirement Wix does not advertise loudly, and how to publish and test. Then you train the AI on your docs so it answers routine questions and hands the rest to you.
Read the guide →Adding live chat to Squarespace takes one snippet in Settings, Advanced, Code Injection, Footer. It loads on every page, survives template and design changes, and loads async so it does not dent your Lighthouse score. Full steps inside.
Read the guide →Carrd is built for one tiny page, so a chat widget has to stay light. Here is how to add a 6 KB live chat to a Carrd Pro site using the Embed element set to Code, or the site-wide head include.
Read the guide →A precise, Bubble-specific guide to installing a live chat widget. Where to paste the script inside Settings, how it survives Bubble page changes, and how to identify users who are logged in behind Bubble auth.
Read the guide →A plain notion.site page cannot run custom scripts, so most Notion live chat tutorials are wrong from the first step. This guide covers the two routes that actually work: a Notion site builder with code injection, or a tiny self-hosted wrapper page. Then it shows how to point the AI at the Notion docs you already maintain.
Read the guide →Blogs, documentation and storefronts — same snippet, grounded on your own content.
Skip the heavyweight chat plugin. Add live chat to WordPress with one script on the wp_head hook, via a code-snippets plugin or your child theme's functions.php, so it loads on every page and survives theme updates. Then point muro's AI at your posts and docs so most questions answer themselves.
Read the guide →Add live chat to Shopify with one snippet in theme.liquid: no per-seat app from the App Store, works on every storefront page. Then let muro's AI answer shipping, returns and sizing questions from your own policies, and hand off to you by email for anything order-specific.
Read the guide →Adding live chat to a Ghost blog takes one script in Settings, Code injection, Site Header. It loads on every post and page, and with your own AI key the bot can answer reader questions straight from your published posts.
Read the guide →Docusaurus visitors are mid-problem, which makes docs the best chat surface you own. This guide covers the scripts array trap, the src/theme/Root.js install that actually works, and how to point muro's AI at your docs so the widget answers from the pages your users are already reading.
Read the guide →Three ways to add a live chat widget to a WooCommerce store: a snippet plugin, a wp_head hook in functions.php, or a child theme's header.php. Plus the caching plugin settings that hide widgets from shoppers, and how to train an AI on your shipping and returns policies so it converts pre-sale questions and hands order issues to you.
Read the guide →Most teams already use one of five platforms — Shopify, WordPress, Webflow, Wix, or Next.js. Here's the exact path through each one's admin to get muro live in five minutes.
Read the guide →Wire the inbox into your own agents and tools over MCP, the REST API and webhooks.
The Model Context Protocol lets your AI agent act on real systems. muro exposes your support inbox as an MCP server, so the agent in your code editor can read and answer customers.
Read the guide →ChatGPT supports remote MCP servers through custom connectors, and muro hosts one at a stable URL. This guide walks through creating a scoped API key, adding the connector, and what the eight tools let ChatGPT actually do: read conversations, draft and send replies, and triage your inbox without copy-paste.
Read the guide →GitHub Copilot in VS Code can call MCP servers in agent mode, which means it can read your customer conversations, not just your code. Here is the full setup with muro's hosted MCP server: one scoped API key, a few lines in .vscode/mcp.json, and a triage-fix-reply loop that never leaves the editor.
Read the guide →Automation platforms speak HTTP, and so does muro. Point a webhook at your catch hook to trigger flows, and call the REST API to send replies back. No server to host.
Read the guide →A chat that never reaches your CRM is a lead you forgot. Push contacts in real time with webhooks, or pull them in batches with the REST API. Here is both, with code.
Read the guide →[FAQ]
Paste one script tag into your site’s <head> (or the site-wide embed setting on a no-code builder). The widget loads asynchronously from muro.chat, weighs about 6 KB gzipped, and works on any site that lets you add a snippet — no SDK, no build step, no npm install.
Any site where you can add a <script> tag: React, Next.js, Vue, Nuxt, Remix, Astro, SvelteKit, Rails, Laravel and Django on the code side; Webflow, Framer, Wix, Squarespace, Carrd, Bubble and Notion on the no-code side; plus Ghost, Docusaurus, WordPress, WooCommerce and Shopify. There are step-by-step guides for each above.
No. On no-code builders like Webflow, Framer, Wix, Squarespace and Carrd you paste the snippet into a single site-wide head or custom-code field and it appears on every page. On frameworks, it is one line in your layout or root template.
No. It is roughly 6 KB gzipped vanilla JavaScript, loads asynchronously so it never blocks your content, and renders inside a Shadow DOM so it can’t touch your CSS or your Lighthouse score.
When you turn it on, muro’s AI answers each visitor from your own published docs and product context, in the visitor’s language, and hands off to a human the moment it isn’t sure. You can also bring your own Anthropic key for unlimited AI at zero markup.
One snippet, unlimited agents, one flat price across every project. 14-day trial, no card, cancel in a click.