Skip to main content
Glama
atoolz

flyte-mcp

by atoolz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to flyte-mcp

No user-submitted related servers found.

    Related Servers

    • Internal Documentation Search

      aklianeva
      F
      license
      A
      quality
      Not graded
      maintenance
      Exposes an internal engineering knowledge base to AI assistants, allowing users to search and retrieve standards, runbooks, and architecture decisions. It supports RAG-enhanced search, document scraping, and specialized prompts for incident investigation and code reviews.
      5
      -

    • Atlas Docs MCP Server

      CartographAI
      A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.
      5
      13 npm
      36
      MIT

    • Crawl4AI RAG MCP Server

      adnan0758
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to crawl, index, and retrieve information from technical documentation using semantic search, with optional knowledge graph validation for code hallucination detection.
      MIT
    • Kedro MCP Server by kedro-org

      Kedro MCP Serverofficial

      kedro-org
      A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with versioned guidance for Kedro projects, including notebook conversion and project migration.
      3
      229 PyPI
      3
      Apache 2.0
    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

    B3.3/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Flyte: documentation retrieval, example exploration, plugin details, symbol lookup, execution status, task execution, code migration, and search. There is no overlap in purpose.

    Naming Consistency5/5

    Tool names follow a consistent imperative verb_noun pattern with underscores (e.g., get_flyte_, list_flyte_, find_flyte_, run_flyte_task). The naming is predictable and uniform across the set.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 range, but each tool serves a unique and necessary function for the Flyte ecosystem. The count is well-scoped and not excessive.

    Completeness4/5

    The tools cover the primary use cases for interacting with Flyte: documentation, examples, symbols, plugins, runs, task execution, and migration. Missing features like workflow creation are outside the intended scope, so there are no significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources