F
licenseNot graded
qualityC
maintenanceEnables AI coding agents to plan, build, and review websites and product interfaces with a persistent, user-led process, including design direction, component contracts, and implementation review.
-
@briefgate/mcp
by sekera-radim
Related Servers
Alternatives to @briefgate/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to vet a developer's shipped products, check fixed pricing and availability, and submit project briefs on behalf of users.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create projects, post rich status updates with images and video, claim tasks, read replies, and gate work behind user approvals over a live browser dashboard.2 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to collaborate on the same project by sharing session briefs and reading each other's native transcripts, memories, and instructions in place, with zero-copy, across different agent tools.58 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to connect and interact with common business platforms like Shopify, WordPress, and Calendly via pre-built connectors for tasks such as product management, content operations, and scheduling.13MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates with the AgentCraft framework to enable secure communication and data exchange between AI agents, supporting both premade and custom enterprise AI agents.3-
TDQS
A4.2/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct resource-action pair: intakes, items, folders, recipients, webhooks, and auth are cleanly separated. Even get_intake_status vs get_intake_results are clearly differentiated as progress tracking vs value retrieval. No two tools have overlapping purposes that would cause misselection.
Naming Consistency4/5
The set mostly follows a consistent verb_noun snake_case pattern (list_folders, get_intake_results, add_items, update_item, manage_webhook). Minor deviations exist: 'login'/'logout' lack an object, and 'define_intake' uses a different create verb than 'create_folder', but the overall pattern remains predictable.
Tool Count5/5
15 tools is well within the appropriate range for a dedicated intake-management product. Each tool serves a necessary role across auth, folders, intake lifecycle, item management, recipients, and webhooks, with no redundancy or bloat.
Completeness4/5
The core lifecycle is well covered: create, read status and results, update intakes/items, add items, request revisions, send chases, manage recipients and webhooks. The main gap is the lack of an explicit archive or delete tool for intakes (the archived state is referenced but not actionable via MCP), and no direct remove-item operation, though these are workaroundable via the dashboard.
Maintenance
ActivityMaintained
ResponsivenessNo issues