why_it_worked — RipClip MCP Tool
why_it_worked
(why it worked) is one of 44 tools on the
RipClip
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call why_it_worked from your client
- Claude Code RipClip why_it_worked run in your project directory
- Claude Desktop RipClip why_it_worked ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RipClip why_it_worked ~/.cursor/mcp.json
- VS Code RipClip why_it_worked .vscode/mcp.json
- Zed RipClip why_it_worked ~/.config/zed/settings.json
- Windsurf RipClip why_it_worked ~/.codeium/windsurf/mcp_config.json
- Cline RipClip why_it_worked ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RipClip why_it_worked ~/.gemini/settings.json
- Grok RipClip why_it_worked .mcp.json (in your project root)
- ChatGPT RipClip why_it_worked Settings → Connectors → Advanced → Developer mode
- Claude.ai RipClip why_it_worked Settings → Connectors → Add custom connector
- LangChain RipClip why_it_worked pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ripclip https://ripclip.org/mcp/Other tools on this server
- list_projects
- list_clips
- list_library
- import_video
- estimate_hu
- find_clips
- job_status
- get_download_link
- list_social_accounts
- draft_post
- get_post_stats
- best_time_to_post
- edit_clip
- plan_posts
- weekly_report
- search
- fetch
- edit_catalog
- style_clip
- add_to_clip
- translate_captions
- preview_frame
- adjust_look
- frame_clip
- retime_clip
- mix_audio
- undo_edit
- import_photo
- save_template
- explain_clips
- find_moments
- get_moments
- clip_range
- list_clipping_presets
- write_captions
- update_draft
- delete_draft
- compare_platforms
- whats_taking_off
- get_account_stats
- show_clips
- show_drafts
- show_report
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.