Skip to content

docs(registry): simpler plugin submission form - #2311

Merged
AnishSarkar22 merged 2 commits into
MODSetter:devfrom
AnishSarkar22:docs/plugin-submit-form-wording
Oct 21, 2026
Merged

AnishSarkar22 merged 2 commits into
MODSetter:devfrom
AnishSarkar22:docs/plugin-submit-form-wording

Conversation

@AnishSarkar22

@AnishSarkar22 AnishSarkar22 commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

What

The Submit a plugin issue form (.github/ISSUE_TEMPLATE/plugin-submit.yml) is simpler and says what's supported:

  • Intro:
    • one sentence on what happens: a bot checks the server and comments, and editing the issue checks it again;
    • then a short We support list: remote MCP servers on a public HTTPS address, Streamable HTTP or the older HTTP+SSE, and sign-in by none, a key each user pastes, or OAuth. Local (stdio) servers can't be listed yet.
  • Removed: the paragraph about checking tools with the MCP Inspector, and the sentence about a reviewer signing in. The form's own "How a reviewer signs in" field still covers that.
  • One-line description: the hint says it's the line on the plugin's page, not its card.
  • Tool names: the hint asks for every tool, including the ones the server lists only after sign-in.
  • Who can use it: the choices are now Free (a free account is fine) and Paid: users need a plan or subscription you sell. The old "Needs an account or subscription the publisher sells" read as if a free Notion account made a plugin paid.
  • Before you send: the checkbox reads "There's no key, token or password in this issue."

The submission check matches the form's text word for word, so FREE and PAID in registry_check/submission/issue_form.py and the tests' sample answers change with it. test_issue_form.py reads the form's choices with their quotes removed, because a choice containing a colon has to be quoted in YAML.

Why

The old intro said "Streamable HTTP" only, though the bot also lists SSE servers, and it spent a paragraph on an optional check. Its paid choice described a free account as paid.

Fixes #

How to test

cd plugins/registry/check && uv run pytest -q

All pass. On GitHub, the new form shows once this reaches main, the default branch.

Separately, the form asks for the plugin-submission label, and accepting a submission needs registry: accept. Neither label exists in the repository yet; a maintainer creates them once with gh label create.

🤖 Generated with Claude Code

High-level PR Summary

This PR simplifies the plugin submission form for the registry by clarifying what types of MCP servers are supported (remote servers with HTTPS, not local stdio), rewording the access tier choices to better distinguish free vs paid plugins, and updating the intro to be more concise. The corresponding validation code and tests are updated to match the new form text exactly.

⏱️ Estimated Review Time: 5-15 minutes

💡 Review Order Suggestion
Order File Path
1 .github/ISSUE_TEMPLATE/plugin-submit.yml
2 plugins/registry/check/registry_check/submission/issue_form.py
3 plugins/registry/check/tests/submission_forms.py
4 plugins/registry/check/tests/test_issue_form.py
5 plugins/registry/check/tests/test_submission.py

Need help? Join our Discord

AnishSarkar22 and others added 2 commits October 21, 2026 16:36
Say what servers the registry supports, drop the Inspector paragraph,
shorten the no-secrets box, and word the access choices as Free and Paid,
so a free account no longer reads as needing one sold by the publisher.
The intake's FREE and PAID match the new choices.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 21, 2026

Copy link
Copy Markdown

@AnishSarkar22 is attempting to deploy a commit to the Rohan Verma's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Oct 21, 2026

Copy link
Copy Markdown

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: Repository: MODSetter/SurfSense/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 94436f91-cb60-4d79-beef-587fc34ab26e
📥 Commits

Reviewing files that changed from the base of the PR and between fde61ef and 13008b4.

📒 Files selected for processing: 5
  • .github/ISSUE_TEMPLATE/plugin-submit.yml
  • plugins/registry/check/registry_check/submission/issue_form.py
  • plugins/registry/check/tests/submission_forms.py
  • plugins/registry/check/tests/test_issue_form.py
  • plugins/registry/check/tests/test_submission.py
+------------------------------------------------------------------------+
| I'm CodeRabbit. I review the code you never knew you needed reviewing. |
+------------------------------------------------------------------------+
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@AnishSarkar22
AnishSarkar22 merged commit 13f16c3 into MODSetter:dev Oct 21, 2026
27 of 30 checks passed
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.

1 participant