August 12, 2026

Introducing Edge MCP — agentify your website

An agent embedded on your website can talk — but when the user says "add the OLED to my cart," the best it can do is point at the button. Edge MCP lets the agent operate the app itself: your site declares which of its real operations an agent may run (products.search, cart.add, checkout.placeOrder), and the agent calls them — the cart opens, the page navigates, the order gets placed.

@napster-corp/edge-mcp is a thin layer on the WebMCP standard: it polyfills document.modelContext in every browser and adds live-state resources and console debugging on top — your registrations stay pure standard WebMCP, so any compatible agent can drive them, the Napster Omniagent included.

What Edge MCP is — and isn't. The rule that explains everything: the agent operates your website through the website's own functions. If the website can do something, the agent can do it. If the website can't, neither can the agent — Edge MCP adds no capabilities your app doesn't already have; it makes the ones you choose callable by an agent.

Start here: the Edge MCP docs — or go end-to-end with Add an AI Agent to Your Website, which combines Edge MCP with the Web SDK to put an agent on your site that can also operate it.