Skip to content

add upsun to claude marketplace#3

Open
ganeshdipdumbare wants to merge 6 commits intomainfrom
add-claude-marketplace
Open

add upsun to claude marketplace#3
ganeshdipdumbare wants to merge 6 commits intomainfrom
add-claude-marketplace

Conversation

@ganeshdipdumbare
Copy link
Contributor

No description provided.

Copilot AI review requested due to automatic review settings March 10, 2026 11:04
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds Upsun as a Claude plugin marketplace entry and updates installation/configuration guidance to match the new marketplace/plugin layout.

Changes:

  • Update README plugin install commands to use upsun@... naming.
  • Add MCP server configuration via a new .mcp.json file and document optional MCP enablement.
  • Add Claude marketplace metadata (.claude-plugin/marketplace.json) and simplify plugin metadata (.claude-plugin/plugin.json), plus a hooks scaffold.

Reviewed changes

Copilot reviewed 5 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
README.md Updates install commands and adds optional MCP server setup instructions.
.mcp.json Introduces MCP server config for Upsun with token placeholder and write-disabled header.
.claude-plugin/plugin.json Simplifies plugin metadata to name + description.
.claude-plugin/marketplace.json Adds marketplace definition that exposes the upsun plugin from this repo.
hooks/hooks.json Adds hooks manifest scaffold (currently empty).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

"plugins": [
{
"name": "upsun",
"source": "./",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Potentially we should put plugin files in a subdirectory, as we don't want to pull .github, evals etc. into the plugin definition itself?

{
"hooks": {
}
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file isn't necessary (neither are the .gitkeep ones)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants