Contributing

MCP Ambassador is Apache 2.0. Contributions are welcome — to the core server, the Ambassador Client, the documentation, or the community MCP registry.

Repositories

Adding an MCP to the registry

This is the highest-value contribution. If you use an MCP that isn't in the registry yet, add it:

1. Fork community-registry
2. Copy an existing YAML definition from registry/ as a template
3. Fill in the fields:
   • name — short identifier (lowercase, hyphens)
   • displayName — human-readable name
   • description — what the MCP does (1-2 sentences)
   • transport — stdio or http
   • command — spawn command (e.g., npx -y @modelcontextprotocol/server-github)
   • env — list of environment variable definitions with name, description, and required: true/false
   • tags — category tags (e.g., [code, version-control])
4. Submit a pull request
5. Maintainers will validate and test before merging

Reporting bugs

Report bugs via GitHub Issues.

Include:

• MCP Ambassador version (docker logs | grep "Server version")
• Docker version (docker --version)
• Operating system
• Steps to reproduce
• Expected vs actual behavior
• Relevant logs (sanitize secrets!)

Feature requests

Open a GitHub Discussion for feature requests. Check the Roadmap first — your feature may already be planned.

Code contributions

1. Fork the repository
2. Create a feature branch
3. Write tests for your changes
4. Ensure all tests pass: npm test
5. Submit a pull request with a clear description

Running tests

npm install
npm run build
npm test
# 327 tests expected to pass

Code standards

• TypeScript strict mode
• ESM modules (import/export, no require)
• Tests for all new API endpoints
• Security-sensitive code gets security review (auth, crypto, credentials)

Security disclosures

Security issues should be reported privately. Use the security label on GitHub Issues, or contact the maintainers directly. Do not disclose publicly until a fix is available.