[alifsayalee]

The plugin regenerator writes each plugin's displayName into the spec as the SDK name (info.title / MergedApiName and CodeGenSettings.ProjectName). For these 14 plugins the display name differs from the name the SDK already carries, so the next regeneration would rename their packages and classes (for example the_plaid_api → plaid), breaking code written against them.

This sets displayName to each SDK's current name, read from sdk-map.md in its C#, Python and TypeScript repos (all three agree), and bumps the patch version in all three manifests. The README table is regenerated with sync_marketplace.py.

Plugin	displayName	Version
finnhub	Finnhub → Finnhub API	0.2.2 → 0.2.3
firecrawl	Firecrawl → Firecrawl API	0.2.2 → 0.2.3
frankfurter	Frankfurter → Frankfurter API	0.2.2 → 0.2.3
google-maps	Google Maps → Google Maps Platform	0.1.1 → 0.1.2
notion	Notion → Notion API	0.1.1 → 0.1.2
nytimes	New York Times → The New York Times APIs	0.1.1 → 0.1.2
plaid	Plaid → The Plaid API	0.1.1 → 0.1.2
shutterstock	Shutterstock → Shutterstock API Explorer	0.3.3 → 0.3.4
slack	Slack → Slack Web API	0.2.2 → 0.2.3
sportsdata	Sportsdata → SportsDataIO	0.2.2 → 0.2.3
spotify	Spotify → Spotify Web API	0.1.1 → 0.1.2
tesla	Tesla → Tesla Fleet Management API	0.2.2 → 0.2.3
twilio	Twilio → Twilio SDK	0.3.3 → 0.3.4
vimeo	Vimeo → Vimeo API	0.2.2 → 0.2.3

The other 10 plugins already match their SDK names. Plugin ids are unchanged, so npx context-plugins install <id> is unaffected. The Claude Code and Cursor plugin pickers will show the new names.

This should be merged before the regeneration run, since the regenerator reads displayName from main.

🤖 Generated with Claude Code