ScreenPost MCP server
Let Claude Code, Claude Desktop, Cursor or any MCP client take the screenshot, record the screen, clean it up and post it to X. It runs locally through ScreenPost on your Mac, and nothing is posted until you approve it.
Download ScreenPost (7-day free trial)
What your agent can do
Capture
take_screenshot, list_windows, list_displays, start_recording, stop_recording, get_recording_status, cancel_recording
Edit
annotate, crop, beautify, redact_secrets, undo, redo, revert_edits, trim_clip, make_gif, get_editor_options, list_beautify_presets
Library and files
list_captures, get_capture, import_media, export, copy_to_clipboard, reveal_in_finder, open_in_editor, extract_text, delete_capture
Write and post to X
count_post_length, enhance_text, compose_post, post_now, schedule_post, open_in_x_compose, list_posts, list_scheduled, cancel_scheduled, retry_failed, set_default_x_account
Share and hand off
create_share_link, update_share_link, revoke_share_link, share_link_stats, upload_media_to_url, get_media_base64
Status and settings
get_status, list_capabilities, get_settings, set_settings, get_request_status
Try asking
- "Take a screenshot of the Simulator window, add an arrow to the new button and post it to X with a short changelog."
- "Record the next 20 seconds of my screen, trim it and make a GIF under X's size limit."
- "Redact any API keys in my last capture, beautify it and export it to my Desktop."
Requirements
- An Apple Silicon Mac with macOS 14 or later, and ScreenPost 1.5 or later installed in
/Applications. - Screen Recording permission for ScreenPost.
- ScreenPost unlocked: the free 7-day trial or a license ($29 once).
- An MCP client that supports stdio servers.
Set it up
- Turn on agents. ScreenPost, Settings, Agents, then switch on Allow agents to control ScreenPost. It is off by default.
- Connect your client. The same pane has one-click Connect buttons for Claude Code, Claude Desktop and Cursor, plus Copy config for anything else.
Claude Code
claude mcp add --scope user --transport stdio screenpost -- /Applications/ScreenPost.app/Contents/Helpers/screenpost-mcp
Start a new session and run /mcp to check that screenpost is connected.
Claude Desktop, Cursor and other clients
{
"mcpServers": {
"screenpost": {
"command": "/Applications/ScreenPost.app/Contents/Helpers/screenpost-mcp",
"args": []
}
}
}
The helper speaks newline-delimited JSON over stdio and needs no arguments or environment variables.
How it stays safe
- Off by default and local only. The helper talks to the running app over a private socket in your user folder. Nothing in these tools goes to a ScreenPost server.
- You approve what goes out. Posting, scheduling, share links, uploads and deletes return awaiting_approval. ScreenPost shows a native sheet with the exact image, text, account and destination, and only you can approve it. No tool approves.
- What you approve is what is posted. The exact bytes you saw are the ones sent, even if the capture changes afterwards.
- Screens are never captured silently. Agent screenshots show a notice and the menu bar shows "agent". You can require approval for every screenshot.
- Secrets stay out. Tools never return license keys, X tokens or API keys, and OCR text comes back with secrets masked.
Questions
Does it cost extra? No. The MCP server is part of ScreenPost: free during the 7-day trial, then $29 once for every feature on 3 Macs.
Is it open source? No. The server ships inside the signed ScreenPost app, so updating the app updates the tools.
Windows or Linux? No, ScreenPost and its MCP server are macOS only.
Questions or a tool you want: [email protected].