ScreenMocks vs Chatpack MCP
A side-by-side look at the ScreenMocks and Chatpack MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
ScreenMocksDeveloper Tools · Remote HTTP/SSEDesign and export App Store / Play Store screenshots, localized across all 48 App Store locales.37FairAuth: not declaredC
Chatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.86ExcellentAuth: no auth requiredVerdict: choose ScreenMocks for developer tools work over a hosted endpoint; choose Chatpack MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose ScreenMocks when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
CChoose Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S ScreenMocks | C Chatpack MCP |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
ScreenMocks tools
No tool names declared yet. Check the project README from the listing page.
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ScreenMocks
{
"mcpServers": {
"screenmocks": {
"url": "https://www.screenmocks.com/mcp"
}
}
}
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
Frequently asked questions
ScreenMocks is categorized under Developer Tools and uses a remote HTTP/SSE transport. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick ScreenMocks for developer tools work and Chatpack MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
ScreenMocks has no declared pricing — check the project's own site. Chatpack MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add screenmocks and chatpack-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ScreenMocks has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Chatpack MCP has 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars.
