WebMCP: Exposing Existing App Features as Agent Tools
Melvin Vivas · X video post · 2026-09-15 · Open on X
Topics: AI Agents, Tool Use & MCP · Level: intermediate
Summary
The creator plans to try WebMCP after seeing a quoted demo. The demo shows an app exposing features it already has, such as batch processing, theme and dark-mode switching and goal tracking, as WebMCP tools. An agent can then call them for you instead of you doing each step by hand.
Key points
- WebMCP lets a web app expose its existing functions as tools that an AI agent can call.
- Example tools: batch processing, changing the theme or dark mode, and checking tracked goals.
- You don't need new features: wrap what the app already does so it can be used manually or by an agent.
- The creator hasn't tried it yet ('will report back').
Resources mentioned
- WebMCP · tool · developer.chrome.com · free
A proposed web standard that lets websites expose tools and context to AI agents through the Model Context Protocol in the browser.
Also in: Jev + WebMCP Solves 100% of Benchmark Tasks at About 112× Lower Cost (Melvin Vivas on X · notes), Docs7: Serving Agent-Readable Documentation to Coding Agents via MCP (Melvin Vivas on X · notes)
Try this
- Try exposing your web app's existing actions as WebMCP tools.
- Add WebMCP tools to one of your own web apps (e.g., theme switching, batch jobs) so an agent can run them.
More in AI Agents, Tool Use & MCP
- How OpenAI's Agentic Software Factory Works (Pragmatic Engineer)
- Coworker v0.6.1: Connect AI Coworkers to Telegram and Discord Bots
- Cut agent costs by giving chore subagents a cheaper model
- OpenResearch: turn a coding agent into a research agent
- Codex orchestrator/subagent skill: Astra or Sol leads, Luna subagents
- Codex traces: picker model is the orchestrator, subagents stay Luna