Skip to main content
Glama
CURRENT_STATUS.md3.35 kB
**Status:** ACTIVE **Last Updated:** 2025-11-17 **Project Type:** Single-Branch --- ## What's Actually Done ### Published to NPM ✅ - **Package Name:** @stacktown/webby@1.0.0 - **Published:** 2025-11-17 - **NPM URL:** https://www.npmjs.com/package/@stacktown/webby - **Organization:** @stacktown (all custom MCP servers now use this scope) ### Package Renaming ✅ - Changed from `@mcp-servers/webby` to `@stacktown/webby` - Part of organization-wide standardization (14 packages total) - All @stacktown packages now published to NPM ### GitHub MCP Server Configuration ✅ - Added missing `@modelcontextprotocol/server-github` to ~/.claude.json - Renamed `config-manager` → `mcp-config-manager` for consistency - GitHub server path: `/home/cordlesssteve/.nvm/versions/node/v20.19.3/lib/node_modules/@modelcontextprotocol/server-github` ### Core Features (Pre-existing) - **11 MCP Tools** across 4 validation categories - **Performance Testing:** PageSpeed Insights, WebPageTest, GTmetrix - **Accessibility Testing:** Axe DevTools, WAVE - **SEO Testing:** PageSpeed Insights SEO - **Security Testing:** Mozilla Observatory, SSL Labs - TypeScript implementation with proper build pipeline - Playwright integration for browser automation --- ## Current Reality Check ### What Actually Works ✅ - Package successfully published to NPM - Dependencies installed and build completed - All 11 MCP tools defined in codebase - TypeScript compilation successful ### What's Not Verified - **Tool Execution:** Haven't tested actual tool execution - **API Integration:** Haven't verified API keys/endpoints work - **Browser Automation:** Haven't tested Playwright integration - **Error Handling:** No end-to-end testing performed --- ## Git Status **Branch:** main **Remote:** Up to date with origin/main **Modified Files:** - `package.json` (name changed to @stacktown/webby) **Recent Commit:** - b005dd7 Initial release of Webby MCP Server v1.0.0 --- ## Known Issues / Blockers None currently identified. Package published successfully. --- ## Next Steps 1. **Test Tool Execution** - Run each of the 11 MCP tools manually - Verify API integrations work correctly - Test browser automation with Playwright 2. **Documentation Updates** - Update README with @stacktown scope - Add installation instructions for NPM package - Document API key setup process 3. **Quality Assurance** - Add test suite for tool execution - Verify error handling - Test with various website types --- ## Session History ### Session: 2025-11-17 (Initialization) **Work Completed:** - Published @stacktown/webby@1.0.0 to NPM - Renamed package from @mcp-servers/webby to @stacktown/webby - Resolved NPM authentication issues (used automation token) - Successfully published alongside 6 other @stacktown packages **Context:** - Part of larger effort to publish all public MCP servers to NPM - Organization-wide rebranding to @stacktown scope - This is the Webby project's first CURRENT_STATUS document (created during session closeout) **Published Packages (7 total):** 1. @stacktown/claude-telemetry-mcp@1.0.0 2. @stacktown/file-converter-mcp@1.0.0 3. @stacktown/layered-memory-mcp@0.1.0 4. @stacktown/namecheap-mcp-server@1.0.0 5. @stacktown/token-analyzer-mcp@1.0.0 6. @stacktown/unity-mcp-server@0.1.0 7. @stacktown/webby@1.0.0

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cordlesssteve/webby-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server