Add Screeny MCP Server#2254
Closed
rohanrav wants to merge 2 commits intomodelcontextprotocol:mainfrom
Closed
Conversation
Member
|
Thanks for your contribution to the servers list. This has been merged in this combined PR: #2370 This is a new process we're trying out, so if you see any issues feel free to re-open the PR and tag me. |
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.
Description
Add Screeny to Community Servers list in README. Screeny is a privacy-first macOS MCP server that enables AI agents to capture screenshots of user-approved application windows, providing visual context for development and debugging tasks.
Screeny
Motivation and Context
I couldn't find an existing MCP server for taking screenshots of desktop applications (while some existed for browsers). As someone starting in mobile development, I needed something to screenshot my iOS simulator and other windows for debugging and development tasks.
I also wanted a privacy-first approach where users pre-approve specific windows that can be captured, and the system technically enforces these restrictions - even if the model tries, it cannot access beyond approved windows. This server solves the issue of manually taking screenshots repeatedly to describe issues while maintaining strict user control over what can be captured.
How Has This Been Tested?
Breaking Changes
No breaking changes, just an addition to the README community server list.
Types of changes
Checklist
Additional context