Moroka MCP for Studios
Connect your agents to Moroka
MCP is the protocol that lets your IDE operate Moroka. You describe the work in a prompt. The agent creates pages, imports content, checks the preview and publishes — through the same platform your team already edits in the visual builder.
Works with
What MCP is, and how it works.
Model Context Protocol connects the AI in your development environment to Moroka. It does not replace the builder. It gives your agent safe access to the work a studio otherwise does by hand, dozens of times over.
- 01
Connect
Add Moroka MCP to Cursor, Claude Code or Codex.
- 02
Describe the work
Write a prompt — a new client site, a content move, a catalog import.
- 03
Review and publish
Check the draft in preview or the visual builder, then publish.
Workspace connection
{ "mcpServers": { "Moroka": { "type": "streamableHttp", "url": "https://mcp.moroka.ai/mcp", "headers": { "Authorization": "Bearer mcp_mrk_YOUR_KEY" } } }}Client websites from your IDE. The builder stays.
Work from the tools you already use
Write prompts in Cursor, Claude Code or Codex. Create client sites, restructure pages, migrate articles and import products without opening a separate editor for every task.
The visual builder is always there
Every page, product and article created through MCP is normal Moroka content. Your team can keep editing it visually whenever that is faster.
Works with
Cursor
Claude
VS Code
Windsurf
Codex
JetBrains- Cursor
- Claude
- VS Code
- Windsurf
- Codex
- JetBrains
- Cursor
- Claude
- VS Code
- Windsurf
- Codex
- JetBrains
- Cursor
- Claude
- VS Code
- Windsurf
- Codex
- JetBrains
What you can do with Moroka MCP.
One connection covers the same parts of Moroka your studio already works in. Nothing is bolted on the side.
Moroka MCP
Sites
Create and configure projects.
Pages
Create, duplicate and restructure pages.
Builder
Add sections, move blocks, change content and styles.
News
Create and update articles.
Catalog
Create products, categories and bulk imports.
Media
Bring assets into Moroka Media Storage.
Design System
Read typography, colors and responsive rules.
Preview
Render current draft changes.
Visual Feedback
Capture desktop, tablet and mobile screenshots.
Publish
Publish reviewed websites and CMS content.
A real move, not a demo.
We used Moroka MCP to create a client website, migrate 140 WordPress posts automatically, and import 60 products with photos, descriptions and prices. The whole job took 20 minutes and saved more than 20 hours. We billed the client $400 for the move.
- 140
- WordPress posts moved automatically
- 60
- Products with photos, descriptions and prices
- 20 min
- Total time for the whole job
- 20+ hours
- Manual work saved
- $400
- Billed to the client for the move
What is free. What uses credits.
Reading a project costs nothing. Credits are used when MCP creates or changes the site and its content.
No MCP work charge
Read sites and pages
No charge.
Inspect Builder capabilities
No charge.
Read the design system
No charge.
Preview changes
No charge.
Capture screenshots
No charge.
Import media
No MCP work charge. Normal storage limits still apply.
Publish completed work
No charge.
Uses Moroka Credits
- Create pages
- Duplicate page structures
- Make structured page changes
- Create and update articles
- Create and update products
- Bulk content operations
- Large imports and productivity actions
Agency and White Label already include Moroka Credits for this work. If you need more, top them up — nothing changes in how the team works. Credits follow the work that got done, not the number of MCP calls.
The builder is still there.
You just don't have to live inside it.
Build visually when you want to. Work through MCP when speed matters.
Moroka Journal