Framework for deriving reusable, application-specific MCP servers from web applications through controlled exploration and semantic operation inference.
.claude/skills/learn-webapp/— The learning skill that explores web apps and generates MCP servers.claude/skills/webmcp/— The runtime routing skill that intercepts web app tasks and routes them through learned MCP serverssrc/templates/— Templates used during MCP server code generationsrc/utils/— Utility scripts (repository management, manifest handling)MCPs/— Generated MCP server packages (one directory per application)docs/— Project documentationskills/— Shareable copies of skills (synced with.claude/skills/)catalogue.json— Maps applications to their MCP servers (supports multiple MCPs per app)
- All generated code uses ES modules (
"type": "module") - Generated MCP servers use
@modelcontextprotocol/sdkandpuppeteer-core - MCP entries are stored as directories under
MCPs/<app-name>/ - Each generated server includes a
manifest.jsondescribing its capabilities - Every generated server includes a
show_scriptstool for JavaScript introspection
- Learning skill:
.claude/skills/learn-webapp/SKILL.md - Runtime routing skill:
.claude/skills/webmcp/SKILL.md - MCP server template:
src/templates/mcp-server-template.mjs - Application catalogue:
catalogue.json - GitHub repository:
ApartsinProjects/AutoWebMCP
-
WebMCP (runtime): When the user asks to interact with a web app, this skill fires first. It checks
catalogue.jsonfor a matching MCP server, downloads it from GitHub if needed, and routes through semantic tools instead of raw browser clicks. -
learn-webapp (learning): When no MCP server exists for an app, or the user explicitly asks, this skill explores the app and generates a new MCP server. Includes a mandatory user approval gate before code generation.