jake/mcpengine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
mcpengine/infra/factory-tools/mcp-inspector/AGENTS.md
Jake Shore f3c4cd817b Add all MCP servers + factory infra to MCPEngine — 2026-02-06 
=== NEW SERVERS ADDED (7) ===
- servers/closebot — 119 tools, 14 modules, 4,656 lines TS (Stage 7)
- servers/google-console — Google Search Console MCP (Stage 7)
- servers/meta-ads — Meta/Facebook Ads MCP (Stage 8)
- servers/twilio — Twilio communications MCP (Stage 8)
- servers/competitor-research — Competitive intel MCP (Stage 6)
- servers/n8n-apps — n8n workflow MCP apps (Stage 6)
- servers/reonomy — Commercial real estate MCP (Stage 1)

=== FACTORY INFRASTRUCTURE ADDED ===
- infra/factory-tools — mcp-jest, mcp-validator, mcp-add, MCP Inspector
  - 60 test configs, 702 auto-generated test cases
  - All 30 servers score 100/100 protocol compliance
- infra/command-center — Pipeline state, operator playbook, dashboard config
- infra/factory-reviews — Automated eval reports

=== DOCS ADDED ===
- docs/MCP-FACTORY.md — Factory overview
- docs/reports/ — 5 pipeline evaluation reports
- docs/research/ — Browser MCP research

=== RULES ESTABLISHED ===
- CONTRIBUTING.md — All MCP work MUST go in this repo
- README.md — Full inventory of 37 servers + infra docs
- .gitignore — Updated for Python venvs

TOTAL: 37 MCP servers + full factory pipeline in one repo.
This is now the single source of truth for all MCP work.
2026-02-06 06:32:29 -05:00

1.4 KiB
Raw Blame History

MCP Inspector Development Guide

Note: Inspector V2 is under development to address architectural and UX improvements. During this time, V1 contributions should focus on bug fixes and MCP spec compliance. See CONTRIBUTING.md for more details.

Build Commands

  • Build all: npm run build
  • Build client: npm run build-client
  • Build server: npm run build-server
  • Development mode: npm run dev (use npm run dev:windows on Windows)
  • Format code: npm run prettier-fix
  • Client lint: cd client && npm run lint

Code Style Guidelines

  • Use TypeScript with proper type annotations
  • Follow React functional component patterns with hooks
  • Use ES modules (import/export) not CommonJS
  • Use Prettier for formatting (auto-formatted on commit)
  • Follow existing naming conventions:
    • camelCase for variables and functions
    • PascalCase for component names and types
    • kebab-case for file names
  • Use async/await for asynchronous operations
  • Implement proper error handling with try/catch blocks
  • Use Tailwind CSS for styling in the client
  • Keep components small and focused on a single responsibility

Project Organization

The project is organized as a monorepo with workspaces:

  • client/: React frontend with Vite, TypeScript and Tailwind
  • server/: Express backend with TypeScript
  • cli/: Command-line interface for testing and invoking MCP server methods directly