Retire MCP packages and keep Skills support#2694
Draft
quanru wants to merge 1 commit into
Draft
Conversation
Deploying midscene with
|
| Latest commit: |
bc5a4be
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://efc6ff14.midscene.pages.dev |
| Branch Preview URL: | https://codex-retire-mcp-keep-skills.midscene.pages.dev |
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
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
This PR retires Midscene's MCP server surface and keeps the Skills / platform CLI workflow as the supported agent integration path.
Changes
agent-toolsso Skills and platform CLIs can keep using the reusable tool definitions without exposing MCP servers.MIDSCENE_MCP_CHROME_PATHas a deprecated alias forMIDSCENE_CHROME_PATHso existing Puppeteer-mode Skills setups do not break during migration.Why
Midscene no longer needs to ship MCP servers now that Skills cover the agent-driven workflow. Keeping both surfaces increases package, build, docs, and test maintenance cost. This change removes the MCP runtime surface while preserving the lower-level tool definitions required by Skills and platform CLIs.
Validation
pnpm --dir packages/shared exec vitest --run tests/unit-test/chrome-path.test.ts tests/unit-test/env/global-config-manager.test.tspnpm --dir apps/report exec vitest --run tests/report-template-utils.test.tspnpm exec nx build @midscene/shared --skip-nx-cache --verbosepnpm --dir apps/report run buildpnpm exec nx build @midscene/core --skip-nx-cache --verbosepnpm run type-check:testspnpm run lintgit diff --checkNotes for Reviewers
MIDSCENE_MCP_CHROME_PATHvariable is intentionally kept only as a migration alias.dist/is not committed.