Skip to main content
Glama
inbarajaldrin

MCP Tools Orchestrator

by inbarajaldrin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Tools Orchestrator

No user-submitted related servers found.

    Related Servers

    • InfiniteMCP

      day50-dev
      F
      license
      Not graded
      quality
      D
      maintenance
      A meta-MCP server that acts as a universal gateway, allowing users to discover and execute tools from thousands of other MCP servers through semantic search. It dynamically loads servers on demand and provides standardized functions for searching, discovering, and running tools across the entire MCP ecosystem.
      6
      -

    • Magg

      sitbon
      A
      license
      B
      quality
      A
      maintenance
      A meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.
      16
      85 PyPI
      142
      AGPL 3.0

    • FlowMCP

      PeterGreenAppliedAI
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that exposes deterministic workflows as tools, allowing small models to reliably orchestrate APIs and other MCP servers with minimal parameters.
      2
      10 npm
      2
      MIT

    • Lodestar MCP Server

      kanlanc
      F
      license
      C
      quality
      D
      maintenance
      This is an MCP server that facilitates building tools for interacting with various APIs and workflows, supporting Python-based development with potential for customizable prompts and user configurations.
      1
      -

    • programmatic-mcp

      alesya-h
      A
      license
      Not graded
      quality
      D
      maintenance
      A meta MCP server that orchestrates other MCP servers by lazily connecting to them and exposing their tools as JavaScript libraries. It allows users to execute JavaScript code that programmatically interacts with multiple MCP servers within a unified environment.
      12 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one discovers available MCP tools and signatures, while the other executes composed Python that orchestrates those tools. There is no overlap in resource or action, so an agent can easily select the right tool.

    Naming Consistency5/5

    Both names use consistent snake_case and follow a clear verb_noun pattern: execute_composed_code and list_available_tools. The convention is predictable and readable.

    Tool Count3/5

    Only two tools are provided for an orchestration server, which is thin even if the pair is focused. Each tool earns its place, but the surface lacks supporting operations like session management or execution status checks.

    Completeness4/5

    Discovery and execution are the core operations needed for code-based orchestration, and both are present. Minor gaps remain around session lifecycle management (e.g., listing, resuming, or deleting saved sessions) and direct cancellation controls.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources