Repository navigation
Proposal: MCP as a thin client over REST (single whatsmeow session) #780
grigoreo-fox
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I'd like to discuss a possible architecture change around MCP support.
Current limitation
Right now GOWA can run either in
restormcpmode, but not both at the same time.As documented, this comes from the underlying whatsmeow library (one live WebSocket / session per device store).
Idea
Instead of running MCP as a second mode that also opens a whatsmeow client, what if MCP became a thin layer on top of the existing REST API?
In other words:
restmode (one whatsmeow session)/send/message,/app/status, group endpoints, etc.)Benefits
Questions
I'm happy to implement a working prototype (or a full PR) if this direction makes sense to you.
Thanks!
All reactions