.prompts vs ScreenMocks
A side-by-side look at the .prompts and ScreenMocks MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredS
ScreenMocksDeveloper Tools · Remote HTTP/SSEDesign and export App Store / Play Store screenshots, localized across all 48 App Store locales.37FairAuth: not declaredVerdict: choose .prompts for developer tools work; choose ScreenMocks for developer tools over a hosted endpoint. 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | . .prompts | S ScreenMocks |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 38/100 · Fair | 37/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
.prompts tools
No tool names declared yet. Check the project README from the listing page.
ScreenMocks tools
No tool names declared yet. Check the project README from the listing page.
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.
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
ScreenMocks
{
"mcpServers": {
"screenmocks": {
"url": "https://www.screenmocks.com/mcp"
}
}
}
Frequently asked questions
.prompts is categorized under Developer Tools and uses an install path we have not confirmed yet. ScreenMocks belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick .prompts for developer tools work and ScreenMocks 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. .prompts has no confirmed install command yet — follow its own setup instructions.
.prompts has no declared pricing — check the project's own site. ScreenMocks has no declared pricing — check the project's own site. 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 prompts and screenmocks as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, .prompts has a quality signal of 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. ScreenMocks has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.