chore: remove outdated MCP server and its deployment - #71
Closed
contextualbeer wants to merge 1 commit into
Closed
Conversation
The MCP server npm deploy was failing and the package is no longer maintained. Removes packages/mcp-server along with its CI upload, publish workflow steps, release-please entries, and README section. Co-authored-by: Cursor <cursoragent@cursor.com>
Author
|
SDK builder will take care of this |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
packages/mcp-serversubpackage entirely — its npm deploy was failing and the server is no longer maintained (confirmed with founder).publish-npm.yml, and the MCP version-bump entries inrelease-please-config.json.scripts/build, and MCP-only ignore entries (.dockerignoredeleted,.gitignore/.prettierignoretrimmed).The main
context.devpackage is untouched and its publish flow works as before.Test plan
yarn install --frozen-lockfilesucceeds./scripts/buildpasses (tsc, attw, publint all green)./scripts/lintpassescontext.devonlyNote: this repo is Stainless-generated — if the MCP target is still enabled in the Stainless config, the next codegen run will regenerate it. Disable it there as well.
Made with Cursor