The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →EdgeOne Pages MCP lets an MCP client deploy static web content to Tencent EdgeOne Pages and return a public access link. The documented service has two connection modes: a local stdio server started with npx edgeone-pages-mcp, and a remote Streamable HTTP server at https://mcp-on-edge.edgeone.app/mcp-server. Choose the local mode when you need to deploy a folder or ZIP package; the documented HTTP mode does not support those package deployments.
Choose the connection mode first
| Mode | Client configuration | Folder or ZIP deployment | Token | Best use |
|---|---|---|---|---|
| Local stdio | Runs npx edgeone-pages-mcp on your machine |
Supported when authenticated | EDGEONE_PAGES_API_TOKEN is required for authenticated folder or ZIP deployment |
Deploying a packaged site or selecting a Pages project |
| Remote Streamable HTTP | Connects to https://mcp-on-edge.edgeone.app/mcp-server |
Not supported according to the guide | No local token setting is shown in the remote configuration | Using the hosted MCP endpoint for supported requests |
The endpoint and documented behavior can change, so check the current EdgeOne Pages MCP documentation when configuring a new client. Do not treat the remote endpoint as equivalent to the local server: the package-deployment limitation is material.
What you need before setup
- An MCP client that accepts either a local command server or a Streamable HTTP server.
npxavailable in your local Node.js installation for the stdio option.- Your static site as one HTML file, a folder, or a ZIP archive.
- An EdgeOne API token if you will deploy a folder or ZIP through the local server.
- The name of an existing Pages project if you want to deploy into that project rather than create one.
A single HTML file is treated differently from a package. The guide says a single-file deployment receives a temporary link. Use a folder or ZIP when the deployment should be associated with a Pages project.
Option A: configure the local stdio server
Use the documented configuration shape
Add a server entry to your MCP client’s configuration file. The file location and UI label differ by client, but the server definition is:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors#1 Best Overall
{
"mcpServers": {
"edgeone-pages-mcp-server": {
"command": "npx",
"args": ["edgeone-pages-mcp"],
"env": {
"EDGEONE_PAGES_API_TOKEN": "",
"EDGEONE_PAGES_PROJECT_NAME": ""
}
}
}
}Save the file, restart or reload the MCP client, and look for the EdgeOne Pages tools in the client’s connected-server list. Some clients ask for the same values through a graphical form; enter npx as the command, edgeone-pages-mcp as the argument, and add the two environment variables.
Set the API token for packaged deployments
Put the token in EDGEONE_PAGES_API_TOKEN when deploying a folder or ZIP. A blank value is not an authenticated packaged-deployment configuration. Keep the token private: do not commit it to a project, paste it into a public prompt, or place it in client configuration that is synchronized publicly.
EdgeOne’s token documentation describes tokens as identity credentials and asks you to select an expiration when creating one. The listed expiration choices range from one day to one year. Create the token in the EdgeOne Makers console using the current token workflow, then copy it only into the protected environment-variable field used by your MCP client.
Select or create a Pages project
EDGEONE_PAGES_PROJECT_NAME is optional. Set it to the name of an existing project when the deployment belongs there. Leave it empty when you want the guide’s new-project behavior: EdgeOne creates a new Pages project for the deployment.
Option B: connect to the remote Streamable HTTP server
Use your MCP client’s “add remote server” or equivalent command and enter:
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
https://mcp-on-edge.edgeone.app/mcp-serverThe remote configuration is useful when you do not want to run npx locally. However, the official guide explicitly says this mode does not support deploying folders or ZIP packages. If your site consists of multiple assets—such as CSS, JavaScript, images, or fonts—use the local stdio configuration for the documented package flow instead.
Deploy content and interpret the result
Single HTML file
Ask the MCP client to deploy the HTML file or provide it through the Pages MCP tool exposed by the connected server. The documented result is a temporary public link. Temporary means you should not use this flow as the basis for a permanent project URL without confirming the current Pages behavior.
Folder or ZIP package
- Put the complete static site in one folder, preserving relative paths, or create a ZIP containing that folder’s site files.
- Connect through the local stdio server.
- Provide the package to the Pages deployment tool and use the configured project name if targeting an existing project.
- Wait for the deployment response and open the returned public link.
- Check that the HTML, stylesheets, scripts, images, and client-side routes load from the returned URL.
If you left the project name empty, the guide says a new Pages project is created. If you used a project name, verify that the response identifies the intended project before treating the deployment as complete.
What a successful response should tell you
Expect a public access link or deployment result from the MCP tool. The important distinction is whether the request was a single-file temporary deployment or a folder/ZIP deployment associated with a Pages project. Record the returned URL and project name in your release notes; the MCP guide does not establish a universal response schema or a guaranteed deployment-time statistic.
Troubleshooting
The client says the command cannot be found
Confirm that Node.js and npx are installed and visible to the account running the MCP client. In a graphical client, the process may use a different PATH than your terminal. Configure the full path to npx if the client allows it, then restart the client.
Rank #3
The server starts but packaged deployment fails authentication
Check that EDGEONE_PAGES_API_TOKEN is present in the server’s env object, has not expired, and was copied without surrounding quotation marks becoming part of the value. Tokens are required for authenticated folder or ZIP deployment in the documented stdio flow.
The deployment goes to an unexpected project
Inspect EDGEONE_PAGES_PROJECT_NAME. A typo can select a different existing project or prevent the intended association. To follow the documented new-project behavior, clear the value rather than leaving an old project name in the client configuration.
The remote server rejects a folder or ZIP
This is an expected limitation of the documented Streamable HTTP mode. Reconnect using the local stdio server and configure an API token for the packaged deployment.
Only the HTML loads; assets are missing
Use a folder or ZIP instead of a single-file request, and check that asset paths are relative to the deployed site root. A single HTML file cannot carry separate CSS, JavaScript, image, or font files unless they are embedded or otherwise available at their referenced URLs.
The returned link is not permanent
The guide specifically describes a temporary link for a single HTML file. For a project-associated deployment, package the site as a folder or ZIP and use the local authenticated flow.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Security and operational guidance
- Store the API token in the MCP client’s protected environment settings, not in source control.
- Choose the shortest token expiration that fits the deployment job; the documented choices span one day through one year.
- Use a separate token for automation when your console workflow supports it, and revoke or replace credentials that may have been exposed.
- Keep the project name explicit in production automation so a deployment cannot silently create a new project because an environment variable was omitted.
- Test the returned public link from a clean browser session and inspect network requests for missing assets before sharing it.
Do not confuse Pages MCP with other EdgeOne MCP examples
Self-hosted Pages MCP template
The self-hosted template is a separate route. Its documentation describes deploying your own remote MCP service and lists KV storage plus custom-domain binding as setup requirements. Those requirements do not belong to the hosted Pages Deploy MCP configuration above.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
ChatGPT Apps starter
The ChatGPT Apps starter is an EdgeOne Pages project built with Next.js and edge functions; its MCP endpoint is mapped to /mcp after deployment. It is a template for building a ChatGPT app, not a prerequisite for connecting an MCP client to Pages Deploy MCP.
MCP on Edge demo
The MCP on Edge example is a distinct Makers-hosted MCP client/server demonstration with its own model-gateway environment variables. Installing it is not required for Pages MCP deployment.
CLI naming context
EdgeOne’s broader CLI documentation recommends the edgeone makers namespace for local development. It says the edgeone pages namespace is not being phased out at the current stage and would only be phased out after a transition period and advance notice. That guidance does not establish a replacement for the edgeone-pages-mcp package, so keep the MCP server command exactly as documented and verify live CLI documentation before changing automation.
Or skip the browser setup
If your goal is simply to capture the deployed URL as an image or PDF, ScreenshotNeo provides a one-request website screenshot API and MCP server. It accepts cookie and consent banners before capture, removes more than 60 known consent platforms plus newsletter popups and chat widgets, and bills only clean shots: bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Every response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers.
Recommended Free Tools
For the full option list and authentication details, see the ScreenshotNeo documentation. A direct request looks like this:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo also offers an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to try it.
Frequently Asked Questions
Can I use the remote MCP endpoint for a ZIP deployment?
No. The documented Streamable HTTP mode does not support folder or ZIP deployment; use the local stdio server with an API token.
What happens when the project-name variable is empty?
The guide says EdgeOne creates a new Pages project.
Is the self-hosted Pages MCP template required?
No. It is a separate deployment route that requires its own KV storage and custom-domain setup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
