FrameThrower vs Chatpack MCP — MCP Server Comparison | AllMCPs
FrameThrower vs Chatpack MCP
A side-by-side look at the FrameThrower and Chatpack MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose FrameThrower for developer tools work over a hosted endpoint; choose Chatpack MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose FrameThrower when
You need dedicated capabilities in the Developer Tools domain.
You prefer a remote HTTP/SSE transport.
You want tools like search_frames, find_by_craft, find_similar.
search_framesSearch the FrameThrower cinematography reference library by concept, mood, color, composition, or scene. Returns reference frames with film/credits metadata, a preview thumbnail, the full-resolution image URL (use this one for slide decks and documents), a precomputed DEPTH MAP url (greyscale, same dimensions as the frame — pass it straight to a depth ControlNet or any image-to-image pipeline that wants geometry), and a link to view on FrameThrower.
find_by_craftFind frames by specific cinematography craft attributes — lens character, shot size, visual style, setting, time of day, director, or year range. All optional; combine to narrow. Use this to refine a search precisely.
find_similarFind frames visually/semantically similar to a given frame id (from a prior result). Use this to pull more references like one the user shortlisted.
get_frame_detailsGet the full metadata + preview thumbnail + full-resolution image URL + depth map URL + link for a single frame id. The depth map is precomputed and free — use it when the user is generating images and needs the composition or camera geometry of this frame.
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.
get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.
get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.
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.
FrameThrower is categorized under Developer Tools and uses a remote HTTP/SSE transport. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick FrameThrower for developer tools work and Chatpack MCP 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.
FrameThrower has no declared pricing — check the project's own site. Chatpack MCP is listed as free. Auth: no auth required. 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 framethrower and chatpack-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FrameThrower has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Chatpack MCP has 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars.
Retrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.