Appmixer MCP
Related Servers
Alternatives to Appmixer MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes internal company services as LLM-callable MCP tools, enabling AI agents to perform business operations like customer management, order processing, and support ticketing through natural language.-
- AlicenseAqualityBmaintenanceEnables AI agents to perform go-to-market workflows such as company and contact enrichment, CRM querying, and controlled, audited writes to a CRM through MCP tools callable from any MCP client.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables plain-English workflow automation across connected tools like GitHub, Notion, Slack, and more, with self-healing execution, scheduling, and status reporting through MCP.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets you expose any product, web app, or SaaS backend as a dynamic, stateful MCP server with built-in agent memory, context persistence, and workflow-aware tool gating for AI agents.7 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables an LLM to dynamically discover and call tools across multiple MCP servers (file, GitHub, SQL, Python execution) with authentication, rate limiting, and observability, supporting parallel execution and secure deployment.-

qadam-flowofficial
AlicenseNot gradedqualityAmaintenanceSelf-hosted workflow automation platform with a built-in MCP server. Lets AI agents build, validate, publish and run automations, and call any of its 238 integrations (Slack, Telegram, Google Sheets, Notion, ...) as tools.5MIT
TDQS
Scored across 37 tools
Most tools target a clearly distinct resource+action (flow lifecycle, versions, stores, unprocessed messages, components, accounts), and descriptions explicitly disambiguate close pairs like create_flow/update_flow/clone_flow and validate_flow/test_flow/start_flow. A few boundaries remain thin, notably trigger_component vs read_component_trigger (split only by HTTP method) and get_flow_accounts vs list_accounts, but guidance is sufficient to pick correctly.
All 37 tools follow a consistent snake_case verb_noun pattern (get_flow, list_flows, create_store, delete_store_record, retry_unprocessed_message, restore_flow_version). No mixed casing or vague bare verbs, and the noun portion reliably names the resource.
37 tools is heavy, but Appmixer is a genuinely broad platform (flow authoring, execution, triggers, logs, versions, stores, components, accounts, modifiers) and nearly every tool maps to a real operation. Still, some could be consolidated (e.g. list/get unprocessed message, trigger vs read trigger), so the surface feels larger than ideal.
Coverage is strong: full flow CRUD plus start/stop, validation, test-run, logs, status, versioning/clone, data store CRUD, unprocessed-message lifecycle, component/app/account discovery, and modifiers. Minor gaps exist (no delete/compare flow versions, no account connection by design), but no obvious dead ends for core workflows.