@quikrun/mcp
Related Servers
Alternatives to @quikrun/mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to create, retrieve, update, and manage n8n workflows through the n8n API. Supports full workflow lifecycle management including activation, deactivation, and deletion operations.3939 npmMIT
- FlicenseBqualityCmaintenanceEnables AI assistants to manage Sciple platform content including environments, services, dashboards, runbooks, projects, and tickets through the Sciple REST API.6034 PyPI-
- FlicenseNot gradedqualityCmaintenanceEnables ChatGPT to manage n8n workflows through the official REST API. Supports creating, updating, deleting, and running workflows with execution status monitoring.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage n8n workflow automation instances through tools for workflow CRUD operations, execution monitoring, and webhook triggering. It facilitates programmatic interaction with n8n instances via the n8n API with AI-optimized descriptions and error handling.62MIT
- AlicenseBqualityDmaintenanceEnables AI agents to create, update, and manage short links through your Dub.co account, allowing for creation, modification, and deletion of custom shortened URLs.433 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create and manage visual automation configurations, workflows, and UI states through the Qontinui API. It supports project management, workflow execution, and configuration handling for automated web interactions.AGPL 3.0
TDQS
Scored across 9 tools
Each tool targets a distinct action or aspect of snippet management. There is minor potential confusion between update_snippet and update_snippet_code, but descriptions clearly differentiate settings updates from code updates. All other tools are unambiguous.
All tools follow a consistent verb_noun pattern (e.g., list_snippets, get_snippet, create_snippet, delete_snippet). The only minor deviation is list_snippets using plural, which is standard for collection operations. Overall, the pattern is highly predictable.
With 9 tools, the server is well-scoped for snippet management. Each tool serves a necessary function in the lifecycle, and there is no redundancy or bloat.
The tool set covers the full snippet lifecycle: create, read, update (settings and code), delete, duplicate, run, and deploy. This provides complete coverage without any obvious gaps that would hinder typical workflows.