MuninCRM, knowledge, content, outreach, conversations, and analytics in one MCP-first system. Agents do the work across the same tools and data; your team sets the guardrails, approves, and steps in where it matters.
Set up a chat widget, a CMS blog, and analytics in a single Lovable prompt. Lovable builds the frontend — Munin spins up the operations behind it.
Munin puts CRM, KB, CMS, Outreach, Conversations, and Analytics on one backend, one Postgres schema, one identity model, and one MCP endpoint. The dashboard and the agents are using the same product — not parallel systems joined later.
Contacts, companies, deals, pipelines, segments, and activities — with merge proposals and consent controls built in. Shared customer context other workflows read from and update.
crm_create_contact( )crm_find_contact( )crm_log_activity( )+27 moreSpaces and markdown documents with version history, audience scoping, and hybrid search. The knowledge layer agents can search and humans can review.
kb_search( )kb_create_document( )kb_restore_version( )+14 moreCollections, entries, locales, assets, scheduled publishing, and delivery APIs. Structured content for teams that want more than docs and drafts.
cms_create_collection( )cms_create_entry( )cms_publish_entry( )+25 moreApproval-first outbound campaigns built from CRM segments. Agents draft proposals, humans approve them, and compliance checks run before anything goes out.
outreach_create_campaign( )outreach_list_proposals( )outreach_propose_initial( )+6 moreShared inbox workflows for email, widget chat, SMS, and voice — with assignment, handover, claims, topics, and shared KB/CRM context behind every thread.
conv_send_message( )conv_search_messages( )conv_request_handover( )+27 morePrivacy-first page-view and search tracking with trackers, traffic sources, top subjects, and contact journeys — engagement signals other workflows can read and act on.
analytics_create_tracker( )analytics_list_trackers( )analytics_export_events( )+14 moreCustomers reach you over four channels. Six modules share one backend. External admin agents work through MCP — and an internal runner answers chats and curates knowledge from inside the box.
CRM, KB, CMS, outreach, conversations — every workflow Munin runs is exposed as an MCP tool at mcp.getmunin.com. Same backend as the dashboard. Same data as your team.
Munin supports scoped OAuth for user-authorized agents, plus admin and channel-bound API keys where they fit better. Access is scoped and enforced at the tool layer — not bolted on at the edge.
tool: crm_list_contacts_in_segment segmentId: "cseg_a1b2c3d4e5f6g7h8i9j0klmn" → eligible contacts returned tool: kb_search query: "trial conversion — pricing FAQ" limit: 3 → relevant KB hits returned tool: outreach_propose_initial campaignId: "ocp_q2_winback" contactId: "cct_anna" draftSubject: "Still evaluating support automation?" draftBody: "..." → proposal created · pending review
Open source under MIT — fork it, audit it, extend it.
Munin exposes every workflow as MCP tools. Bring any model — Claude, ChatGPT, Cursor, your own — and shape it into whatever agent your business needs. The recipes below are starting points, not the menu.
Every recipe is a prompt + a list of tool scopes. Point Claude, ChatGPT, Cursor, Goose — or your own runner — at the same MCP endpoint and the agents go to work.
Munin gives you more than one operating mode. Some workflows are autonomous. Some escalate to a teammate. Some create reviewable drafts for approval. The common thread is that access is scoped, actions are visible, and riskier AI work stays reviewable.
The agent gathers, drafts, and proposes. The human does the judgment. Edit a draft and the model learns the diff. Reject and the activity history records why.
winback-prospects-q2. Consent and compliance checks ran clean. Awaiting approval to schedule.Same code. Same MCP endpoint. Same Postgres schema. Pick the path that matches what your team can take on — switch any time, your data follows you.
Real OSS. The whole suite, running on your hardware, your cloud, your terms.
docker compose up — the whole stack on one hostReady in five minutes, EU-hosted, no card. The whole suite — for solo builders, small teams, and proofs-of-concept.
For teams running real customer work on Munin. Higher caps, priority support — metered overage instead of hard cliffs.
Same code, same protocol — you choose where it runs.
We built Munin in a month and gave the code away under MIT. Not as charity — as the business model. A field note on why, when software stops being scarce, the only moat left is being trusted to operate it.
Why we put CRM, KB, CMS, Outreach, and Conversations behind a single Postgres — and how row-level security carries the load.
The next generation of business software won't be drawn by designers — it'll be called by agents. A field note on what that means for the shape of CRM, helpdesks, and the people who used to click "Send".
A short argument for why the protocol matters more than the UI, and why we're betting the company on it being open.
Open source. Open protocol.
One stack, your terms.