remove Vessel MCP server#245
Merged
Merged
Conversation
nahiyankhan
marked this pull request as ready for review
July 20, 2026 20:42
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.
Category: improvement
User Impact: Vessel remains available as a component registry without exposing or maintaining a separate MCP server.
Problem:
vessel-reactcarried an MCP binary, server implementation, build target, dependencies, and documentation that are outside its intended role as a private reference component system.Solution: Remove the MCP implementation and packaging surface, simplify the build to the component library, and update repository documentation to describe Vessel accurately.
Validation:
pnpm --filter @design-intelligence/vessel-react build: passedpnpm --filter @design-intelligence/vessel-react typecheck: passedpnpm build: passedpnpm test: 192 passed, 1 skippedpnpm check: passedChangeset: not needed because
vessel-reactis private and the public@design-intelligence/ghostpackage is unchanged.ghost Review:
ghost check --base main: not run because this removes private-package infrastructure without changing a generated surface or fingerprint.ghost review --base main --include-memory: not run because no UI generation behavior or fingerprint semantics changed.File changes
.gitignore
Removes the obsolete
dist-mcpbuild-output rule.CLAUDE.md
Describes Vessel as a component registry and reference component system rather than an MCP server.
README.md
Updates the repository package table to remove the MCP claim.
packages/vessel-react/README.md
Removes MCP build and host setup instructions.
packages/vessel-react/package.json
Removes the MCP binary, output, build target, and direct MCP/Zod dependencies.
packages/vessel-react/src/mcp/bin.ts
Deletes the MCP stdio entry point.
packages/vessel-react/src/mcp/data.ts
Deletes MCP-specific registry data access.
packages/vessel-react/src/mcp/resources.ts
Deletes MCP resource registration.
packages/vessel-react/src/mcp/server.ts
Deletes MCP server construction.
packages/vessel-react/src/mcp/tools.ts
Deletes MCP tool registration.
packages/vessel-react/tsconfig.mcp.json
Deletes the MCP TypeScript build target.
pnpm-lock.yaml
Removes the Vessel MCP and unused Zod dependency edges.
tsconfig.json
Removes the root project reference to the MCP build target.
Screenshots/Demos: N/A