feat: publish to registry

[paoloricciuti]

Partially address #42

Something to figure out:

1. Currently, I fetch a pinned version of mcp-publisher...they suggest fetching the latest, but that feels like an absurd safety hazard. Should we find a way to automate the update of that?
2. Similarly, we should technically find a way to keep the release version in the package.json in sync with the version in server.json...can changesets do that? Another option would be to write a custom step in the release.yml workflow that pushes the change in the open PR, but I currently have no idea how to do it.
3. This also means that we only push to the registry when we publish a new version of the package...I think this is probably fine, but since we release the remote one on merge, it will mean the two will be slightly out of sync. Not a big deal imho.
4. We could technically use svelte.dev as the name instead of io.github.sveltejs, but we need to add a TXT DNS record. Not a big deal, we just need to decide if we want to do it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 11cd244

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@sveltejs/mcp	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
mcp	Ready	Preview	Comment	Oct 5, 2025 10:18am