I have been building websites for more than 20 years, and AI has completely changed how quickly we can create them.
But I kept running into the same problem: generating code is only one part of building a real website.
After the AI writes the HTML, you still need to manage files, hosting, SSL, domains, forms, databases, and future edits. For someone who is not a developer, this final part can be more difficult than creating the website itself.
That is why I built the Orivox MCP website builder.
What is Orivox MCP?
Orivox MCP connects Claude directly to the Orivox website platform using the Model Context Protocol.
Instead of opening another AI website builder, purchasing AI credits, and learning a new editor, you can describe the website you want directly inside Claude.
For example: Create a modern website for a local moving company in Haifa. Add a services section, customer reviews, a WhatsApp button, and a contact form.
Claude understands the request, while Orivox performs the actual website operations.
It creates the project, generates the website files, provides a working preview, and allows Claude to continue making changes.
Editing the website through conversation
After the first version is created, you can continue talking naturally:
Make the header smaller.
Change the colors to dark blue and white.
Add another service.
Replace the main image.
Create an About page.
Connect my domain.
Add a registration form and database.
The important difference is that the conversation is connected to a real website project. Claude is not simply returning a block of code that you must copy somewhere else.
When a change is requested, Orivox updates the actual website.
Claude does the thinking
I designed the system so that each side has a clear role.
Claude handles the conversation, planning, content, and decisions. Orivox handles the website infrastructure: creating and editing files, hosting the project, publishing it, securing it, connecting domains, and managing website features.
You use your own Claude account, so Orivox does not charge you for separate AI calls or sell additional AI credits.
This also means that you can keep working in an interface you already know instead of moving between an AI chat, a code editor, a hosting dashboard, and a domain-management panel.
Why use MCP for this?
MCP gives an AI assistant controlled access to external tools.
A normal chatbot can explain how to publish a website. An MCP-connected assistant can actually perform the authorized steps.
That distinction is what interested me most.
I did not want Claude to only generate instructions such as “upload this file to your server.” I wanted it to safely create the project, update it, and prepare it for real visitors.
The user remains in control and connects their Orivox account through an authorization process. Claude can then access the website-building tools associated with that account.
Who is it for?
I think this approach is particularly useful for:
Small-business owners who do not want to learn web design.
Developers who want to create and test websites quickly.
Freelancers building websites for customers.
Claude users who prefer working through conversation.
Anyone who wants a real hosted website rather than another code snippet.
It will not replace every development workflow. Complex applications can still require developers, custom architecture, and manual testing.
But for business websites, landing pages, prototypes, and many database-backed projects, speaking to an AI can be a much simpler starting point.
Try it The project is still evolving, and I am continuing to improve it based on real usage.
You can learn more and connect Claude here:
I would genuinely appreciate feedback from other developers experimenting with MCP. I am especially interested in hearing which website operations you would want an AI assistant to handle automatically.