Add v2 feedback issue template
Adds a v2 feedback issue template, mirroring the one on the TypeScript SDK (v2-feedback.yml) so v2 pre-release feedback lands in a consistent shape across both SDKs.
Motivation and Context
With v2 pre-releases out, we want a low-friction path for reporting anything that broke, surprised, or slowed people down — including API-design friction and docs gaps, which the existing bug template doesn't really invite. The TypeScript SDK already has this template; this is the Python equivalent.
Adaptations from the TS version:
- Labels with
v2-alpha(this repo's label for feedback against published v2 pre-releases;v2here is scoped to ideas/plans). - Docs links point to https://py.sdk.modelcontextprotocol.io/v2/ and the migration guide.
- Repro block renders as Python; version hint is
pip show mcpinstead ofnpm ls. - Area dropdown drops "codemod" (no Python codemod).
How Has This Been Tested?
YAML validated locally; the form renders once merged to main.
Breaking Changes
None.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed
Additional context
The existing bug template remains; v2 reporters now have a dedicated entry point. Mirroring typescript-sdk #2397, the README v2 callout and the docs landing banner now deep-link to the prefilled template (issues/new?template=v2-feedback.yaml), with Discord kept as the secondary channel.