Modulex MCP is live.
Claude can now see the workflows you've built in ModuleX and run them from the chat.
Your workflow library is already inside the conversation.
One message, and the work starts.
one URL in.
it pulls the real headline, CTAs and pricing off the page, then hands back a roast and 10 fixes with the replacement copy already written.
not "improve your headline." the actual new headline.
i built a workflow that roasts landing pages.
obviously, mine went first.
it found our best selling point buried halfway down the page.
then it found a line in the pricing section that basically says the product might not work.
it also counted 9 CTAs. four of them go to the same signup page. apparently i really want you to sign up.
can’t even argue with it.
drop your url.👇 i’ll run a few from the replies.
this is what we built Files for.
the SOP, policy, and ticket stay in Modulex. the workflow reads them, waits for approval, then saves the final record back to the same folder.
most company files just sit in folders.
i wanted mine to run the work.
Files just landed in @modulexdev.
i added:
a support guide
a refund policy
a sample customer ticket
a few minutes later, it generated:
read the ticket → check the policy → mark urgency → draft a reply → wait for human approval → save the final record back to Files
the customer had been charged twice.
the workflow found the duplicate, confirmed it was eligible for a refund, drafted the response, then stopped for approval.
the files weren't attachments anymore.
they were running the process.
what file would you turn into a workflow?
Most company research starts with 20 tabs and ends with a doc nobody trusts.
We built a different interface for company research.
one URL → 3 research tools → claim validation → 5 ranked growth plays → a 6-page company x-ray.
still researching companies tab by tab?
all i gave @modulexdev was the ElevenLabs URL and 3 sentences.
a few minutes later, it generated:
Firecrawl tears through the site → Exa maps competitors → Tavily hunts 180 days of signals → analyst writes the report → validator tries to break every claim → weak sections get repaired → 5 growth plays get ranked → human approval
one URL went in.
5 growth plays and a 6-page company x-ray came out.
drop your company or closest competitor.
i’ll run 3 from the replies and post every report.
still building workflows node by node?
i described the outcome in 3 sentences.
a few minutes later, @modulexdev generated:
google maps → company research → email verification → lead scoring → approval → sheets
no nodes picked.
no connections drawn.
you don't start by building the graph.
you describe the outcome and get it back.
the more workflows i look at, the stranger this feels:
ai can write your code and read a 100-page contract in seconds.
meanwhile, half your job is still:
copy from email
paste into the crm
copy that
paste into slack
we gave computers intelligence.
humans are still the api between apps.
what do you still copy-paste every day?
asked our assistant to find our biggest customer risk.
it searched Slack, found the conversation, and drafted a Gmail reply...
then waited.
by default, no customer email goes out without human approval.👇
sending something sensitive to a client or your boss? you probably don't want the AI just... sending it.
so drop an interrupt node in and it waits for your approval first.
don't need it? leave it out, let it run fully automatic.
your call, every time.
Most AI assistants know the internet.
Your team needs one that knows your company.
Upload your documentation once: support guides, policies, whatever your team leans on. Then just ask.
Instead of hallucinating, the assistant searches your knowledge base first. It answers from your own documents, source cited.
No switching tabs. No "I think the policy was somewhere..."
the best automations are the ones you forget you set up. they just run without you.
describe the outcome once.
pick when it runs.
every morning. every 5 minutes. every first monday of the month. whatever fits, in your timezone.
and every version you ship is saved, so you can roll back to the exact one that worked, or call the same workflow through an API whenever you need it.
new landing page is live.
we stripped out most of the marketing copy and tried to show the product instead.
tell us what to fix.
https://t.co/iWVFIlQ6e7
Today, we're launching ModuleX, the AI workspace that's already connected to everything.
⋅ 200+ integrations built in: connect the tools you use in one click
⋅ Composer: say what you want, it builds the workflow on a visual canvas
⋅ One engine: the same workflow runs in chat, on the canvas, and through the API
⋅ Bring your own keys or use ours, zero markup, with human approval where you want it
Built to actually do the work, not just chat about it.
https://t.co/eEc1TJbmOu
And you're not stuck doing it solo. Build with your team on the same canvas, live, then run it in chat, on the canvas, or through the API. Stuff ships faster when nobody's waiting on a handoff.
Want Tavily, Firecrawl or ElevenLabs in the mix? Already on, no signup. We bring the keys for a handful of premium tools and we're adding more. Rather use your own? Go ahead, no markup.