Skip to main content
Glama

Related Servers

Alternatives to Agentled MCP Server

Related Servers

  • F
    license
    Not graded
    quality
    Not graded
    maintenance
    Universal AI API Orchestrator. 850 tools across 53 services under a single MCP interface. Connect Claude, GPT, or Gemini to Stripe, Slack, GitHub, LinkedIn, Cloudflare, Shopify, Twilio, and 46 more via natural language. $0.10/execution, no subscription. Patent Pending.
    266 npm
    5
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables plain-English workflow automation across connected tools like GitHub, Notion, Slack, and more, with self-healing execution, scheduling, and status reporting through MCP.
    3 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides 300+ MCP tools for orchestrating AI agents — including swarm coordination, self-learning memory, and task management — enabling MCP clients like Claude Code and Cursor to spawn, coordinate, and learn from specialist agents across sessions.
    15,746 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Open source AI agent platform with MCP server, browser automation, knowledge packs, and workflow engine. Works with Claude Code, ChatGPT, Cursor, and any MCP client.
    30 npm
    5
    Apache 2.0

TDQS

A3.7/5.0

Scored across 40 tools

Disambiguation4/5

Most tools have distinct purposes with clear boundaries, such as chat for conversation, create_workflow for building, and get_workflow for retrieval. However, some overlap exists between tools like get_execution and get_timeline, which both retrieve execution details, and between update_workflow and update_step, which could cause confusion about when to use each for modifications.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, such as create_workflow, delete_workflow, list_workflows, and get_workflow. This predictability makes it easy for agents to understand and navigate the toolset without ambiguity in naming conventions.

Tool Count2/5

With 40 tools, the count is excessive for the workflow management domain, leading to potential cognitive overload and redundancy. While the server covers many operations, a more streamlined set of 15-25 tools would likely suffice without sacrificing functionality, making this overly heavy for typical agent use.

Completeness5/5

The toolset provides comprehensive coverage for workflow management, including full CRUD operations (create, read, update, delete), execution control (start, stop, retry), import/export capabilities, testing tools, and knowledge graph interactions. No significant gaps are apparent, ensuring agents can handle end-to-end workflows effectively.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive