Skip to content

chore: deprecate @zuplo/mcp in favor of @modelcontextprotocol/sdk#71

Open
ntotten wants to merge 2 commits into
mainfrom
claude/flamboyant-aryabhata-178c37
Open

chore: deprecate @zuplo/mcp in favor of @modelcontextprotocol/sdk#71
ntotten wants to merge 2 commits into
mainfrom
claude/flamboyant-aryabhata-178c37

Conversation

@ntotten

@ntotten ntotten commented May 10, 2026

Copy link
Copy Markdown
Member

Summary

Marks @zuplo/mcp as deprecated and points users to the official MCP TypeScript SDK, @modelcontextprotocol/sdk.

Changes

  • README.md — adds a prominent > [!WARNING] deprecation callout at the top with a link to the official SDK, and rewords the description to past tense.
  • package.json — updates description and adds a deprecated field with the migration message.

Why

The official @modelcontextprotocol/sdk now covers the use cases this package was built for. New projects should adopt it directly, and existing users should migrate.

Follow-up (manual)

To make npm install @zuplo/mcp actually surface a warning, the package must also be deprecated on the npm registry:

npm deprecate @zuplo/mcp "@zuplo/mcp is deprecated and no longer maintained. Please migrate to the official MCP TypeScript SDK: @modelcontextprotocol/sdk (https://github.com/modelcontextprotocol/typescript-sdk)."

This can only be done by a publisher with credentials to the npm package — it can't happen in CI from this PR.

🤖 Generated with Claude Code

Add a deprecation warning callout to the README and a `deprecated` field
in package.json pointing users to the official MCP TypeScript SDK
(@modelcontextprotocol/sdk). The official SDK now covers these use cases
and is the recommended path forward for new projects and existing users.

Note: `npm deprecate @zuplo/mcp "..."` must still be run against the
registry to surface the warning at install time.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 10, 2026 22:00

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Deprecates @zuplo/mcp and directs users to the official Model Context Protocol TypeScript SDK (@modelcontextprotocol/sdk), aligning repository docs and package metadata with the project’s end-of-maintenance status.

Changes:

  • Add a prominent deprecation warning callout at the top of the README and reword the package description in past tense.
  • Update package.json description to indicate deprecation and add a deprecation/migration message.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
README.md Adds a deprecation warning banner and updates wording to reflect that the SDK is no longer maintained.
package.json Updates package description and adds a deprecation/migration message in metadata.

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

Comment thread package.json Outdated
"version": "0.1.0",
"description": "A fetch API based, remote server first, TypeScript SDK for MCP.",
"description": "DEPRECATED — please use the official @modelcontextprotocol/sdk instead.",
"deprecated": "@zuplo/mcp is deprecated and no longer maintained. Please migrate to the official MCP TypeScript SDK: @modelcontextprotocol/sdk (https://github.com/modelcontextprotocol/typescript-sdk).",
The `deprecated` field is not a standard npm package.json field and is
ignored by npm when determining whether to show install-time deprecation
warnings — those come from registry metadata set via `npm deprecate`.
Keeping it here risks misleading readers into thinking the package is
already deprecated on the registry. The README warning plus the manual
`npm deprecate` step cover this properly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ntotten

ntotten commented May 10, 2026

Copy link
Copy Markdown
Member Author

Addressed Copilot's review in 7fcc17e — removed the non-standard deprecated field from package.json. The README warning is now the in-repo source of truth, and the registry-side warning will be set via npm deprecate as noted in the PR description.

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.

2 participants