google-flow-mcp-server
Related Servers
Alternatives to google-flow-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Chrome Web Store — upload, publish, status, metadata & Playwright-based UI automation828 npm4MIT
- FlicenseAqualityDmaintenanceAutomated Playwright E2E test repair powered by a self-improving, governed MCP server that runs failing tests, collects failure artifacts, reasons about root causes, validates and applies fixes, and re-runs to verify.12-
- AlicenseAqualityCmaintenanceAn MCP server that assembles CapCut International projects by reading and writing local project files, adding captions, subtitles, overlays, and more so editors start with a mostly-done timeline. It includes tools for inspecting projects, restyling captions, importing subtitles, and rendering alpha-channel overlays via Remotion.81MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for managing LinkedIn content workflows. It generates images via OpenAI, stores assets in Cloudinary, and queues drafts through Buffer with mandatory human approval.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for robust browser automation of legacy web portals, featuring exactly-once execution via an SQLite-backed idempotency lock and resilient Playwright locators.-
- FlicenseAqualityBmaintenanceMCP server for automating consultation and download of documents from Brazil's TRF1 PJe system through authenticated sessions. It uses Playwright for authenticated navigation, providing tools to query process metadata, list documents, and download full case files.61-
TDQS
Scored across 4 tools
Each tool targets a distinct step in the poster workflow: create_project sets up a project, generate_poster creates from scratch, edit_poster refines an existing image, and poster_ratio_editor specifically adjusts aspect ratio. There is minor overlap between edit_poster and ratio_editor, but descriptions clarify the difference.
Three tools follow a verb_noun pattern (create_project, generate_poster, edit_poster), while poster_ratio_editor uses a noun_noun pattern with 'editor' at the end. The tool_ prefix is consistent, but the deviation in the last tool's pattern makes it slightly inconsistent.
With only 4 tools, the server is well-scoped for a specific poster generation and editing workflow. Each tool serves a distinct purpose in the pipeline, and the count feels appropriate without being excessive or thin.
The tool set covers the core lifecycle of creating a project, generating a poster, editing it, and adjusting its ratio. Minor gaps exist (e.g., no delete or listing tool), but the primary workflow is fully supported and agents can complete the intended tasks.