Repository navigation
test: verify actual standalone WeChat MCP stdio interoperability (no account) - #14
Merged
Merged
Conversation
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.
Add an optional integration smoke that installs the independent
eaopen/wechat-providerPython package in an Ubuntu CI runner and uses the shipped Rust Local Bridge CLI to register it, discover its six MCP tools, invokewechat_statusandwechat_searchon an empty temporary DB, and reject a nonexistent tool.This is a real cross-process
initialize → tools/list → tools/calltest, not a JSON-only mock and not a test of personal WeChat, UI/RPA, reading chats or sending messages. The standalone product relationship remains intact; the normal Rust 3-platform CI does not depend on this optional Python workflow. Relates to Local Bridge PR #13 and WeChat Provider issues #1/#2.