Skip to content

docs(mcp): timeout and retry settings (ENG-3329) - #345

Open
harshranjan-ftw wants to merge 1 commit into
mainfrom
harshranjan/eng-3329-mcp-retries-timeouts-and-cancellation
Open

harshranjan-ftw wants to merge 1 commit into
mainfrom
harshranjan/eng-3329-mcp-retries-timeouts-and-cancellation

Conversation

@harshranjan-ftw

@harshranjan-ftw harshranjan-ftw commented Oct 28, 2026 •

Copy link
Copy Markdown

What

Linear: ENG-3329

The MCP page did not list the timeout and retry settings. They were only in the MCP repo's README. This PR adds them to the environment-variable table and adds a short "Timeouts and retries" section. The section explains the whole-call deadline, which writes are not retried after an unclear failure, Retry-After, and cancellation.

Changes

  • plugins/mcp.mdx: HYDRADB_TIMEOUT_SECONDS (default 45) and HYDRADB_MAX_RETRIES (default 2) in the environment-variable table, plus a new "Timeouts and retries" section under Configuration.

Testing

  • mintlify-hygiene check --deny-warnings: passed.
  • No staging or production system was called.

Merge order

  1. MCP: ENG-3329 fix(mcp): one deadline per call, no blind write retries, cancel on hosted MCP hydradb-mcp#117
  2. This docs PR: merge after that change is released, since the new default (45s for the whole call) and the retry rules describe it.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

…ENG-3329)

Signed-off-by: Harsh Ranjan <harsh.ranjan@hydradb.com>
@github-actions

Copy link
Copy Markdown

✅ Mintlify Hygiene

No issues found.

@mintlify

mintlify Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
cortex-ai 🟢 Ready View Preview Oct 28, 2026, 10:07 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@openhack-agent

Copy link
Copy Markdown

✅ OpenHack Summary

Security review of docs(mcp): timeout and retry settings (ENG-3329). 1 changed file; 0 findings at or above the low reporting threshold.

P1: Critical 0   P2: High 0   P3: Medium 0   P4: Low 0

Confidence Score: 5/5

No reportable security findings were detected in this scan.

Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage.

Files Needing Attention: None

Important Files Changed
  • plugins/mcp.mdx (modified)

Last reviewed commit: 603534a · View review on OpenHack


TIP: Mention @openhack-agent in a PR comment to request a review or ask a question. Use @openhack-agent fix all for every finding, or @openhack-agent fix unresolved threads for open review threads only.

@openhack-agent openhack-agent Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OpenHack reviewed this commit. See the OpenHack Summary for the confidence score and fix actions.

@greptile-apps

greptile-apps Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The documentation appears safe to merge once the author's stated MCP release prerequisite is met.

Summary

Adds timeout and retry guidance to plugins/mcp.mdx.

  • MCP users can see how timeout and retry rules affect tool calls.

Reviews (1) · Last reviewed commit: "docs(mcp): timeout and retry settings, a..." · Reviewed by Greptile

@tushar-hydradb tushar-hydradb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This branch was successfully deployed

1 active deployment
staging — 603534a9 Deployed Oct 28, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants