Add mcpName and server.json for MCP Registry#102
Conversation
Decisions: - claim io.mailtrap/mcp namespace via npm mcpName field (registry step 2) - add server.json at repo root per official MCP Registry schema (step 3) - bump to 0.4.1 so mcpName ships in a fresh npm release Co-authored-by: Cursor <cursoragent@cursor.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
📝 WalkthroughWalkthroughVersion 0.4.1 release that introduces a new ChangesVersion 0.4.1 Release with MCP Registry Support
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Changes
mcpName: "io.mailtrap/mcp"topackage.jsonfor npm package-ownership proofserver.jsonwith npm stdio transport and env var declarations0.4.1acrosspackage.json,manifest.json, andsrc/config/index.tsHow to test
No QA needed — registry manifest and npm metadata only, no runtime behavior change.
Summary by CodeRabbit
Release Notes: Version 0.4.1