jake/mcpengine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
mcpengine/infra/factory-tools/mcp-inspector/CONTRIBUTING.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

2.2 KiB
Raw Permalink Blame History

Contributing to Model Context Protocol Inspector

Thanks for your interest in contributing! This guide explains how to get involved.

Getting Started

  1. Fork the repository and clone it locally
  2. Install dependencies with npm install
  3. Run npm run dev to start both client and server in development mode
  4. Use the web UI at http://localhost:6274 to interact with the inspector

Inspector V2 Development

We're actively developing Inspector V2 to address architectural and UX improvements. We invite you to follow progress and participate in the Inspector V2 Working Group in Discord, weekly meetings, and GitHub Discussions (where notes are posted after meetings).

Current version (V1) contribution scope:

  • Bug fixes and MCP spec compliance are actively maintained
  • Documentation updates are always appreciated
  • Major changes will be directed to V2 development

Development Process & Pull Requests

  1. Create a new branch for your changes
  2. Make your changes following existing code style and conventions. You can run npm run prettier-check and npm run prettier-fix as applicable.
  3. Test changes locally by running npm test and npm run test:e2e
  4. Update documentation as needed
  5. Use clear commit messages explaining your changes
  6. Verify all changes work as expected
  7. Submit a pull request
  8. PRs will be reviewed by maintainers

Code of Conduct

This project follows our Code of Conduct. Please read it before contributing.

Security

If you find a security vulnerability, please refer to our Security Policy for reporting instructions.

Questions?

Feel free to open an issue for questions or join the MCP Contributor Discord server. Also, please see notes above on Inspector V2 Development.

License

By contributing, you agree that your contributions will be licensed under the MIT license.