Fix registry metadata ahead of MCP Registry publish [sc-146582] - #3
Merged
Merged
Conversation
- server.json description was over the registry schema's 100-char limit; rewrite it to state any MCP-compatible agent can connect - websiteUrl pointed at https://ifttt.com/docs/mcp, which 404s; use the live https://ifttt.com/mcp product page instead, and align the same link in llms.txt and both READMEs Validated with mcp-publisher validate and scripts/validate.mjs.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: IFTTT/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe change updates IFTTT MCP links to the hosted product page. It also updates the server description to mention automation across 1,000+ services, Applet creation, actions, and queries. ChangesMCP product links
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Prepares
server.jsonfor publishing to the official MCP Registry (sc-146582):descriptionat 100 characters; ours was ~200 and would have failedmcp-publisher publish. The new copy also states explicitly that any MCP-compatible agent can connect (a story acceptance criterion).websiteUrlfixed. It pointed athttps://ifttt.com/docs/mcp, which returns 404. Now points at the livehttps://ifttt.com/mcpproduct page. The same dead link is fixed inllms.txtand both READMEs.Validation
mcp-publisher validate→ ✅ server.json is validnode scripts/validate.mjs→ passedNotes
Publishing itself is a separate step: it needs a one-time DNS TXT record on ifttt.com to verify the
com.iftttnamespace, thenmcp-publisher login dns+mcp-publisher publish. Details on the story.Summary by CodeRabbit