Merged
Conversation
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
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.
Summary
.kiro/settings/mcp.json) to the existing Cursor / Claude Desktop / Windsurf table; renames the heading to "Cursor, Claude Desktop, Kiro & Windsurf". Mirrors the substantive part of the upstream Kiro PR while keeping this fork's section structure.@perplexity-ai/mcp-server, so the badge was misleading.@perplexity-ai/mcp-server+PERPLEXITY_API_KEYand would launch the upstream server) and skips the upstream consolidation that folds VS Code into themcpServerstable (this fork keeps a separate VS Code section documenting theservers/type: stdioschema).Closes #1.
Test plan
README.mdrenders correctly on GitHub: heading reads "Cursor, Claude Desktop, Kiro & Windsurf", table includes Kiro, no npm badge near the title.servers/type: stdioJSON unchanged..github/workflows/upstream-sync.ymlreportsmainis no longer behindperplexityai/modelcontextprotocol@mainfor substantive content (the workflow may still flag pure formatting/badges; if so, that's expected and can be ignored).