AppScreenStudio vs Chrome DevTools MCP
AppScreenStudio lists no tools and runs remotely and Chrome DevTools MCP lists no tools and runs locally.
| Fact | AppScreenStudiocom.appscreenstudio/app-screen-studio | Chrome DevTools MCPio.github.secforge/chrome-devtools-mcp |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Remote | Local |
| Needs first | – | Node.js |
| Licence | Not stated | APACHE-2.0 |
| Latest version | 0.1.0 | 1.10.1004 |
| Known advisories | Not checked yet | 0 |
| Works in | Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | Not known |
| Install | Install AppScreenStudio | Install Chrome DevTools MCP |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare AppScreenStudio with othersCompare Chrome DevTools MCP with others