Skip to content

Add Screeny MCP Server #2254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rohanrav
Copy link

@rohanrav rohanrav commented Jul 1, 2025

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?

  • Tested with Claude Desktop and Cursor on macOS
  • Verified screenshot capture of approved windows in background without focus changes
  • Tested window approval system and permission handling
  • Verified privacy controls - only pre-approved windows accessible
  • Error handling tested (multiple failure scenarios)

Breaking Changes

No breaking changes, just an addition to the README community server list.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant