Skip to content

fix: Show MCP connection errors in the UI - #11495

Merged
mudler merged 4 commits into
mudler:masterfrom
richiejp:fix/mcp-config-metadata
Aug 13, 2026
Merged

mudler merged 4 commits into
mudler:masterfrom
richiejp:fix/mcp-config-metadata

Conversation

@richiejp

Copy link
Copy Markdown
Collaborator

Description

Configured model-level MCP servers disappeared from Chat whenever connection setup or tool discovery failed. That hid actionable errors—including container DNS, routing,
and VPN reachability problems—and the model editor did not explain the expected mcp.remote and mcp.stdio formats.

This change:

  • registers model-editor metadata and examples for remote and stdio MCP configuration
  • keeps configured servers visible and returns a per-server error when discovery fails
  • retries failed discovery while safely closing partially created sessions
  • propagates server status through local and distributed MCP discovery endpoints
  • renders unavailable servers as disabled error rows while leaving healthy servers selectable
  • documents configuration formats, container networking implications, and model/global/client MCP scopes
  • excludes host-only .claude and .tools directories from Docker contexts; validation reduced this checkout's measured context from 2.1 GB to 541.77 MB

No API fields were removed. Healthy MCP servers retain their existing behavior.

Testing

  • Focused Go tests for config metadata, MCP discovery, LocalAI MCP endpoints, and server status propagation
  • React production build
  • React inline-style gate
  • Two Playwright MCP server-status tests
  • docker compose -f docker-compose.dev.yaml config --quiet
  • Scratch BuildKit context transfer measurement

Notes for Reviewers

A model-configured MCP server is now listed even when it cannot be contacted. Its row shows the discovery/setup error and cannot be selected until a later discovery
request succeeds.

  • Yes, I signed my commits.

  • Documentation updated (docs/content/) for user-facing changes.

  • fix(mcp): surface configured server failures

  • build(compose): match CUDA development image

  • revert: keep host build settings out of compose

  • fix(docker): exclude local agent artifacts

Keep model-configured MCP servers visible when discovery or connection setup fails, propagate status through distributed discovery, and let the Chat UI show actionable errors while retrying unavailable servers.

Add model-editor metadata for remote and stdio configuration and document the expected format, deployment networking boundary, and alternate MCP scopes.

Assisted-by: Codex:gpt-5 Ordino golangci-lint
Signed-off-by: Richard Palethorpe <io@richiejp.com>
Configure the API image with the cublas, CUDA 13, auth-tagged build settings used by the local development Makefile invocation, including the 24-way Docker build.

Assisted-by: Codex:gpt-5 Ordino
Signed-off-by: Richard Palethorpe <io@richiejp.com>
The CUDA development deployment is managed from ~/docker/localai, not the repository example Compose file. Restore the generic example and keep machine-specific build settings in the host deployment.

Assisted-by: Codex:gpt-5 Ordino
Signed-off-by: Richard Palethorpe <io@richiejp.com>
Keep Claude worktrees and locally installed verification tools out of the Docker build context. These host-only directories added roughly 1.9 GB to every root image build.

Assisted-by: Codex:gpt-5 Ordino
Signed-off-by: Richard Palethorpe <io@richiejp.com>
@mudler
mudler merged commit 5c63969 into mudler:master Aug 13, 2026
69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants