flyte-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_flyte_versionC | Flyte SDK version this knowledge pack was built from, plus counts. |
| get_flyte_overviewA | Return the flyte-sdk README - high-level description of Flyte V2. |
| get_flyte_featuresA | Return the flyte-sdk FEATURES.md - concise list of V2 capabilities. |
| get_flyte_install_guideA | Return CLI help output and install instructions parsed from flyte-sdk. |
| list_flyte_symbolsA | List public Flyte V2 API symbols. Optional kind filter: function, class, constant. |
| get_flyte_symbolA | Full detail of one Flyte V2 symbol: signature, params, docstring, module path. Accepts "flyte.TaskEnvironment" or just "TaskEnvironment". |
| search_flyte_apiB | Keyword search over Flyte V2 symbol names, signatures, docstrings. |
| list_flyte_patternsD | Canonical example themes from flyte-sdk/examples/. |
| get_flyte_patternB | Return README and example code for a theme (e.g. 'caching', 'genai', 'accelerators'). If file is given, return just that file's snippet. Otherwise README + first file. |
| find_flyte_example_forA | Find example themes best matching a natural-language use case. Searches READMEs and file docstrings across all example themes. |
| list_flyte_pluginsA | List Flyte plugins from the registry. Optional category filter. |
| get_flyte_pluginA | Full detail of a Flyte plugin by slug: package, modules, versions, install command. |
| suggest_flyte_plugin_forA | Given a natural-language need (e.g. 'run Spark', 'connect Snowflake'), suggest plugins. Prefers V2-native entries (sdk='flyte-sdk') over legacy V1 duplicates. |
| migrate_v1_to_v2A | Rewrite flytekit V1 Python code into flyte-sdk V2 syntax. Returns the transformed code plus a list of applied changes and warnings about patterns that need manual review. |
| run_flyte_taskA | Execute a task on the configured Flyte cluster. Requires flyte-sdk installed. module_path: absolute path to the .py file defining the task task_name: Python name of the task function within that file inputs: dict of input kwargs |
| get_flyte_execution_statusB | Fetch current status of a Flyte run by id. |
| list_flyte_recent_runsC | List recent runs from the configured Flyte cluster. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
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.
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.
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.
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.