docs(ai-agents): document MCP connection timeout behavior#742
Closed
mintlify[bot] wants to merge 1 commit into
Closed
docs(ai-agents): document MCP connection timeout behavior#742mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
🤖 Documentation BotStatus🔗 Broken Links (Manual Fix Required)Click to view details |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new 20-second timeout that Lightdash applies when AI agents connect to external MCP servers, and the
MCP_CONNECTION_TIMEOUT_MSoverride for self-hosted deployments.Changes
MCP_CONNECTION_TIMEOUT_MSenv var (default20000) for self-hosted admins who need to tune the timeout.Context
Triggered by lightdash/lightdash#23788, which adds a timeout to MCP client connect and tool-discovery calls so a hanging MCP server no longer stalls admin or chat requests. On timeout, the server is marked as errored with a user-facing message, and per-server timeouts in agent runs prevent one slow server from blocking the rest.