It cannot edit files
There is no write tool in the five. Code changes still happen in the mypage workspace.
MCP
Call mypage from the tool you already have open
Point your MCP client at mypage and stay where you are. Browse the gallery, start a project, and get a preview link back in the same conversation.
Exposed today5 tools
- callable tools
- JSON-RPC dialect
- credits to fork
- planning is read-only
- fingerprint characters
- many calls, one request
Publishing only accepts source that a security scan has already fingerprinted.
What this is
Your agent gets hands inside mypage.
MCP is the shared way an AI tool reaches an outside service. mypage speaks it. So in Cursor you can write “start me a pilates booking site from the gallery” and the tool does the lookup, forks the template, and hands back the project id and preview URL. No tab switching, no copy-paste of ids.
How to use it
Three steps and it is wired.
Nothing to install. Your client already knows how to speak MCP — it just needs the address.
- Add the address
Put the mypage MCP address into your client's server list. There is no installer and no companion app.
- List the tools
Your client shows five: list templates, start from a template, read a project, plan a build, publish.
- Ask in plain language
“Fork the booking starter and tell me the preview URL.” The project id and link come back in the reply.
What the server actually exposes
Five tools, no more.
This list is not a roadmap. It is what the server returns when a client asks for its tool list.
- list_templates
Returns 336 ready-to-use designs with names and summaries. Takes no arguments.
- start_from_template
Clones a slug into a new project and builds its preview. Costs zero credits.
- get_project
Takes a project id and returns its name and current status.
- plan_generation
Returns the steps and files a prompt would produce. It does not run, so it spends nothing.
- deploy_project
Requires the 64-character fingerprint from the current security scan. Only reviewed source ships.
- Batched calls
Send several JSON-RPC 2.0 requests in one array and get the answers back in order.
What it will not do
The honest edges.
Worth knowing before you wire it into an agent loop.
Planning stays a plan
Asking for a plan never starts a build. Running it is a separate, deliberate action.
Publishing without a fingerprint is refused
A stale or missing scan fingerprint is rejected rather than waved through.
We tested our side
The protocol was exercised with real HTTP requests against our server. We have not measured every client's setup screen for you.
Next
Where to go from here
A project started over MCP is an ordinary project. The gallery and the scan page describe the rest of its life.