chore(server): bump server.json to 0.0.3 to match published npm version

[johnxie]

Why

packages/server/server.json pins version 0.0.2, but @taskade/mcp-server on npm only has 0.0.1 and 0.0.3 (latest) — 0.0.2 was never published.

The official MCP Registry validates that packages[].version resolves to a real published npm version carrying the matching mcpName. With 0.0.2, mcp-publisher publish would fail validation. This bump (both the top-level version and packages[0].version → 0.0.3) unblocks the Registry publish.

What this unblocks

Publishing io.github.taskade/mcp-server to registry.modelcontextprotocol.io — which then auto-cascades to PulseMCP (flips its temporary mirror to the canonical entry), and feeds Glama / mcp.so refreshes.

npx @modelcontextprotocol/publisher login github   # auths the io.github.taskade namespace
npx @modelcontextprotocol/publisher publish         # from packages/server, reads server.json

Verified

• ✅ npm @taskade/mcp-server latest = 0.0.3 (0.0.2 absent)
• ✅ mcpName already present in published package: io.github.taskade/mcp-server
• ✅ JSON validates; only the two version strings changed

Context: internal tracker chore(mcp) — Publish to the official MCP Registry.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 41b5511

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[Copilot]

Pull request overview

This PR updates the MCP server registry metadata in packages/server/server.json to reference a real, published npm version of @taskade/mcp-server, aligning the server manifest with what exists on npm so Registry publishing/validation can succeed.

Changes:

• Bump top-level version in packages/server/server.json from 0.0.2 to 0.0.3.
• Bump packages[0].version for @taskade/mcp-server from 0.0.2 to 0.0.3.

---

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

[johnxie]

cc @deanzaka @lxcid — context for review 👇

server.json pinned 0.0.2, but @taskade/mcp-server on npm only has 0.0.1 and 0.0.3 (0.0.2 was never published). The official MCP Registry validates that packages[].version resolves to a real npm version, so a publish would fail as-is. This bumps both the top-level version and packages[0].version → 0.0.3 to match npm.

Pairs with #36 (the OIDC auto-publish workflow). After both merge, one Actions → "Publish to MCP Registry" → Run workflow click registers io.github.taskade/mcp-server in the official registry → cascades to PulseMCP (flips its temporary mirror to the canonical entry), Glama, and mcp.so.

Low risk: only two version strings change; JSON validated.

[johnxie]

Superseded — closing

main already has server.json at 0.0.3 (landed via #38, which synced all four version sources). And #36 adds an auto-sync step that derives server.json's version from package.json at publish time, so this class of drift can't recur.

This PR	Already on main
bump server.json 0.0.2 → 0.0.3	✅ #38 (merged) + auto-sync in #36