llama-stack-mirror/llama_stack/providers/registry
Sébastien Han df6ce8befa
fix: only load mcp when enabled in tool_group (#2621)
# What does this PR do?

The agent code is currently importing MCP modules even when MCP isn’t
enabled. Do we consider this worth fixing, or are we treating MCP as a
first-class dependency? I believe we should treat it as such.

If everyone agrees, let’s go ahead and close this.

Note: The current setup breaks if someone builds a distro without
including MCP in tool_group but still serves the agent API.

Also, we should bump the MCP version to support streamable responses, as
SSE is being deprecated.

Signed-off-by: Sébastien Han <seb@redhat.com>
2025-07-04 20:27:05 +05:30
..
__init__.py API Updates (#73) 2024-09-17 19:51:35 -07:00
agents.py fix: only load mcp when enabled in tool_group (#2621) 2025-07-04 20:27:05 +05:30
datasetio.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
eval.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
files.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
inference.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
post_training.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
safety.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
scoring.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
telemetry.py docs: auto generated documentation for providers (#2543) 2025-06-30 15:13:20 +02:00
tool_runtime.py fix: only load mcp when enabled in tool_group (#2621) 2025-07-04 20:27:05 +05:30
vector_io.py fix: CI flakiness in vector IO tests by pinning pymilvus>=2.4.10 (#2610) 2025-07-04 10:27:23 +05:30