Repository navigation
Conversation
Member
Author
|
This is a wrong approach. The MCP server here is running on Smithery, meaning the CLI is also running on Smithery servers. Which is both slower, and means that it just runs in a container somewhere in the cloud without access to your accounts and files. It also can't run localnet, because there is no Anvil in the cloud. When you make a request, it just spins up a CLI in the cloud, runs a command and streams response back to you. Which is not helpful as a dev tool. Instead, what we should do is make the CLI spin up its own MCP server locally. |
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.
Using zeta-chain/docs#744