Cherry Mcp

This package implements exactly what it claims, but pay attention to these security implications before installing: - Secrets handling: The CLI can save server-specific environment variables into config.json in plaintext. Do not store long-lived API keys there; instead export them in the shell before starting the bridge, add config.json to .gitignore, or use an alternative secret store. - Arbitrary commands: The bridge will spawn whatever command you add to config.json. Only add commands you trust. A misconfigured server entry could run anything on your machine. - Localhost exposure & CORS: Although the server binds to 127.0.0.1, it sets Access-Control-Allow-Origin: '*'. That makes it possible for a malicious website open in your browser to issue requests to the bridge and read responses (same-origin protections defeated by the wildcard CORS). If you run this on a desktop, either remove or restrict the CORS header, enable the IP allowlist, or set strong rate limits and audit logging. - Audit & controls: Enable audit logging and an IP allowlist if you plan to expose tools that act on sensitive accounts. Configure rate limits to reduce impact of automated requests. - Least privilege & isolation: Run the bridge with minimal OS privileges (non-root user) and consider containerizing it. Review every server entry before starting and avoid running untrusted MCP packages under your main account. If you want me to mark specific lines to change (e.g., remove wildcard CORS, harden default config, or prompt before writing env values to config.json), I can produce a patch or recommended code edits. If you need higher assurance, ask the author for provenance or run the bridge in an isolated environment first.