Skip to content

Simplify MCP servers documentation and improve clarity - #1480

Merged
RoiGlinik merged 11 commits into
masterfrom
claude/improve-mcp-docs-nJ4Le
Feb 9, 2026
Merged

RoiGlinik merged 11 commits into
masterfrom
claude/improve-mcp-docs-nJ4Le

Conversation

@aantn

@aantn aantn commented Feb 4, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Significantly streamlined and reorganized the MCP servers documentation to improve clarity and reduce verbosity. The documentation now focuses on practical examples for different deployment scenarios while removing redundant explanations and overly detailed background information.

Key Changes

  • Condensed transport mode descriptions: Reduced verbose explanations to concise, actionable summaries for each transport mode (streamable-http, stdio, sse)

  • Reorganized examples by deployment context: Restructured documentation using tabs to show Holmes CLI, Holmes Helm Chart, and Robusta Helm Chart examples side-by-side, making it easier for users to find relevant configurations

  • Simplified streamable-http section: Removed lengthy configuration structure explanation and consolidated into practical deployment examples with environment variable usage

  • Streamlined stdio documentation:

    • Removed redundant warnings about limitations
    • Consolidated Supergateway setup instructions
    • Simplified Docker and Kubernetes examples
    • Removed verbose comments and placeholder text
  • Removed Supergateway demo section: Eliminated the dedicated "Working with Stdio MCP Servers via Supergateway" section and integrated essential information into the stdio section itself

  • Condensed SSE section: Reduced deprecated SSE documentation to minimal guidance with tab-based examples

  • Reorganized advanced configuration: Moved dynamic headers documentation to a dedicated "Advanced Configuration" section with clearer examples

  • Simplified migration notes: Reduced configuration format change documentation to essential information only

Notable Details

  • Removed ~50 lines of redundant explanations and background information
  • Improved consistency in example formatting across all deployment scenarios
  • Maintained all essential technical information while improving readability
  • Reduced overall documentation length by ~25% while improving usability

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n

Summary by CodeRabbit

  • Documentation
    • Reorganized remote MCP server docs into per-environment guides (Holmes CLI, Holmes Helm Chart, Robusta Helm Chart) with concrete YAML examples and environment-scoped commands.
    • Standardized transport guidance: promoted Streamable‑HTTP, emphasized in-cluster stdio via Supergateway, and deprecated SSE.
    • Moved URL/path guidance into per-server blocks, added llm_instructions and header templating examples, and included migration notes with compatibility warnings.

- Remove redundant Configuration Structure section
- Add 3 tabs (CLI, Holmes Helm, Robusta Helm) throughout
- Inline Supergateway into Stdio Helm tabs
- Move Dynamic Headers to Advanced Configuration section
- Remove Configuration Fields list (examples are self-documenting)
- Remove Default Mode section
- Use bold text instead of subheaders within tabs

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n
Signed-off-by: Claude <noreply@anthropic.com>
@netlify

netlify Bot commented Feb 4, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for holmes-docs ready!

Name Link
🔨 Latest commit 66ee209
🔍 Latest deploy log https://app.netlify.com/projects/holmes-docs/deploys/6989f96db039e50008d938e1
😎 Deploy Preview https://deploy-preview-1480--holmes-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@linux-foundation-easycla

linux-foundation-easycla Bot commented Feb 4, 2026 •

Copy link
Copy Markdown

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: aantn / name: Natan Yellin (66ee209)

@github-actions

github-actions Bot commented Feb 4, 2026 •

Copy link
Copy Markdown
Contributor

✅ Docker image ready for 56c94b2 (built in 1m 1s)

⚠️ Warning: does not support ARM (ARM images are built on release only - not on every PR)

Use this tag to pull the image for testing.

📋 Copy commands

⚠️ Temporary images are deleted after 30 days. Copy to a permanent registry before using them:

gcloud auth configure-docker us-central1-docker.pkg.dev
docker pull us-central1-docker.pkg.dev/robusta-development/temporary-builds/holmes:56c94b2
docker tag us-central1-docker.pkg.dev/robusta-development/temporary-builds/holmes:56c94b2 me-west1-docker.pkg.dev/robusta-development/development/holmes-dev:56c94b2
docker push me-west1-docker.pkg.dev/robusta-development/development/holmes-dev:56c94b2

Patch Helm values in one line (choose the chart you use):

HolmesGPT chart:

helm upgrade --install holmesgpt ./helm/holmes \
  --set registry=me-west1-docker.pkg.dev/robusta-development/development \
  --set image=holmes-dev:56c94b2

Robusta wrapper chart:

helm upgrade --install robusta robusta/robusta \
  --reuse-values \
  --set holmes.registry=me-west1-docker.pkg.dev/robusta-development/development \
  --set holmes.image=holmes-dev:56c94b2

@github-actions

github-actions Bot commented Feb 4, 2026 •

Copy link
Copy Markdown
Contributor

📂 Previous Runs

📜 Run @ f6bbe8a (#21828770326)

✅ Results of HolmesGPT evals

Automatically triggered by commit f6bbe8a on branch claude/improve-mcp-docs-nJ4Le

View workflow logs

Results of HolmesGPT evals

  • ask_holmes: 9/9 test cases were successful, 0 regressions
Status Test case Time Turns Tools Cost
✅ 09_crashpod 36.3s 5 12 $0.2403
✅ 101_loki_historical_logs_pod_deleted 48.6s 6 11 $0.2707
✅ 111_pod_names_contain_service 33.5s 5 11 $0.2240
✅ 112_find_pvcs_by_uuid 36.7s 7 8 $0.2449
✅ 12_job_crashing 35.3s 5 12 $0.2417
✅ 176_network_policy_blocking_traffic_no_runbooks 39.8s 5 13 $0.2478
✅ 24_misconfigured_pvc 37.4s 6 14 $0.2453
✅ 43_current_datetime_from_prompt 5.7s 1 — $0.0118
✅ 61_exact_match_counting 17.0s 4 4 $0.1603
Total 32.2s avg 4.9 avg 10.6 avg $1.8868
📜 Run @ abbecd7 (#21815220527)

✅ Results of HolmesGPT evals

Automatically triggered by commit abbecd7 on branch claude/improve-mcp-docs-nJ4Le

View workflow logs

Results of HolmesGPT evals

  • ask_holmes: 9/9 test cases were successful, 0 regressions
Status Test case Time Turns Tools Cost
✅ 09_crashpod 27.3s 4 10 $0.2050
✅ 101_loki_historical_logs_pod_deleted 54.2s 7 13 $0.3086
✅ 111_pod_names_contain_service 35.2s 5 10 $0.2233
✅ 112_find_pvcs_by_uuid 44.3s 8 10 $0.2809
✅ 12_job_crashing 41.3s 6 14 $0.3978
✅ 176_network_policy_blocking_traffic_no_runbooks 40.4s 6 16 $0.2729
✅ 24_misconfigured_pvc 34.5s 5 14 $0.2276
✅ 43_current_datetime_from_prompt 6.1s 1 — $0.1047
✅ 61_exact_match_counting 17.0s 4 4 $0.1607
Total 33.4s avg 5.1 avg 11.4 avg $2.1814
📜 Run @ 197afdb (#21774254791)

✅ Results of HolmesGPT evals

Automatically triggered by commit 197afdb on branch claude/improve-mcp-docs-nJ4Le

View workflow logs

Results of HolmesGPT evals

  • ask_holmes: 9/9 test cases were successful, 0 regressions
Status Test case Time Turns Tools Cost
✅ 09_crashpod 37.5s 7 12 $0.2635
✅ 101_loki_historical_logs_pod_deleted 39.8s 5 9 $0.2334
✅ 111_pod_names_contain_service 33.0s 5 11 $0.2409
✅ 112_find_pvcs_by_uuid 34.9s 6 7 $0.2334
✅ 12_job_crashing 70.2s 5 10 $0.2207
✅ 176_network_policy_blocking_traffic_no_runbooks 48.2s 6 18 $0.2814
✅ 24_misconfigured_pvc 31.0s 5 14 $0.2250
✅ 43_current_datetime_from_prompt 4.9s 1 — $0.0111
✅ 61_exact_match_counting 12.6s 3 2 $0.1418
Total 34.7s avg 4.8 avg 10.4 avg $1.8514
📜 Run @ 415ebc0 (#21768810160)

✅ Results of HolmesGPT evals

Automatically triggered by commit 415ebc0 on branch claude/improve-mcp-docs-nJ4Le

View workflow logs

Results of HolmesGPT evals

  • ask_holmes: 9/9 test cases were successful, 0 regressions
Status Test case Time Turns Tools Cost
✅ 09_crashpod 32.1s 5 11 $0.2284
✅ 101_loki_historical_logs_pod_deleted 34.9s 4 9 $0.2270
✅ 111_pod_names_contain_service 35.6s 5 11 $0.2246
✅ 112_find_pvcs_by_uuid 38.2s 7 9 $0.2572
✅ 12_job_crashing 35.9s 5 13 $0.2486
✅ 176_network_policy_blocking_traffic_no_runbooks 41.6s 6 15 $0.2766
✅ 24_misconfigured_pvc 41.1s 7 14 $0.2553
✅ 43_current_datetime_from_prompt 5.3s 1 — $0.0110
✅ 61_exact_match_counting 18.6s 4 4 $0.1611
Total 31.5s avg 4.9 avg 10.8 avg $1.8899
📜 Run @ 1084ea9 (#21688197634)

✅ Results of HolmesGPT evals

Automatically triggered by commit 1084ea9 on branch claude/improve-mcp-docs-nJ4Le

View workflow logs

Results of HolmesGPT evals

  • ask_holmes: 9/9 test cases were successful, 0 regressions
Status Test case Time Turns Tools Cost
✅ 09_crashpod 27.3s 4 10 $0.2128
✅ 101_loki_historical_logs_pod_deleted 52.1s 7 12 $0.2955
✅ 111_pod_names_contain_service 34.6s 5 12 $0.2393
✅ 112_find_pvcs_by_uuid 36.1s 6 9 $0.2581
✅ 12_job_crashing 37.9s 6 15 $0.2632
✅ 176_network_policy_blocking_traffic_no_runbooks 51.0s 8 18 $0.3054
✅ 24_misconfigured_pvc 40.4s 7 14 $0.2538
✅ 43_current_datetime_from_prompt 5.5s 1 — $0.1053
✅ 61_exact_match_counting 15.8s 4 4 $0.1585
Total 33.4s avg 5.3 avg 11.8 avg $2.0920

✅ Results of HolmesGPT evals

Automatically triggered by commit 66ee209 on branch claude/improve-mcp-docs-nJ4Le

View workflow logs

Results of HolmesGPT evals

  • ask_holmes: 9/9 test cases were successful, 0 regressions
Status Test case Time Turns Tools Cost
✅ 09_crashpod 31.9s 5 11 $0.2289
✅ 101_loki_historical_logs_pod_deleted 38.9s 5 9 $0.2414
✅ 111_pod_names_contain_service 35.8s 5 11 $0.2227
✅ 112_find_pvcs_by_uuid 35.6s 6 7 $0.2233
✅ 12_job_crashing 35.8s 5 12 $0.2347
✅ 176_network_policy_blocking_traffic_no_runbooks 46.3s 7 17 $0.2935
✅ 24_misconfigured_pvc 39.5s 7 13 $0.2411
✅ 43_current_datetime_from_prompt 5.1s 1 — $0.1049
✅ 61_exact_match_counting 22.8s 4 4 $0.1628
Total 32.4s avg 5.0 avg 10.5 avg $1.9532
📖 Legend
Icon Meaning
✅ The test was successful
➖ The test was skipped
⚠️ The test failed but is known to be flaky or known to fail
🚧 The test had a setup failure (not a code regression)
🔧 The test failed due to mock data issues (not a code regression)
🚫 The test was throttled by API rate limits/overload
❌ The test failed and should be fixed before merging the PR
🔄 Re-run evals manually

⚠️ Warning: /eval comments always run using the workflow from master, not from this PR branch. If you modified the GitHub Action (e.g., added secrets or env vars), those changes won't take effect.

To test workflow changes, use the GitHub CLI or Actions UI instead:

gh workflow run eval-regression.yaml --repo HolmesGPT/holmesgpt --ref claude/improve-mcp-docs-nJ4Le -f markers=regression -f filter=

Option 1: Comment on this PR with /eval:

/eval
markers: regression

Or with more options (one per line):

/eval
model: gpt-4o
markers: regression
filter: 09_crashpod
iterations: 5

Run evals on a different branch (e.g., master) for comparison:

/eval
branch: master
markers: regression
Option Description
model Model(s) to test (default: same as automatic runs)
markers Pytest markers (no default - runs all tests!)
filter Pytest -k filter (use /list to see valid eval names)
iterations Number of runs, max 10
branch Run evals on a different branch (for cross-branch comparison)

Quick re-run: Use /rerun to re-run the most recent /eval on this PR with the same parameters.

Option 2: Trigger via GitHub Actions UI → "Run workflow"

🏷️ Valid markers

benchmark, chain-of-causation, compaction, confluence, context_window, coralogix, counting, database, datadog, datetime, easy, elasticsearch, embeds, fast, frontend, grafana-dashboard, hard, integration, kafka, kubernetes, leaked-information, logs, loki, medium, metrics, network, newrelic, no-cicd, numerical, one-test, port-forward, prometheus, question-answer, regression, runbooks, slackbot, storage, toolset-limitation, traces, transparency


Commands: /eval · /rerun · /list

CLI: gh workflow run eval-regression.yaml --repo HolmesGPT/holmesgpt --ref claude/improve-mcp-docs-nJ4Le -f markers=regression -f filter=

@coderabbitai

coderabbitai Bot commented Feb 4, 2026 •

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Reworks the MCP Servers documentation: removes the old top-level mcp_servers block, moves each server's url under its config, reorganizes transport-mode guidance (streamable-http preferred, stdio via Supergateway emphasized, SSE deprecated), and adds per-environment examples (Holmes CLI, Holmes Helm Chart, Robusta Helm Chart) plus migration notes.

Changes

Cohort / File(s) Summary
Docs: MCP servers (single file)
docs/data-sources/remote-mcp-servers.md
Complete rewrite and reorganization of the MCP Servers doc: replaced legacy transport-mode wording, removed top-level mcp_servers layout in favor of per-server config blocks (with url relocated under config), standardized transport recommendations (streamable-http, stdio via Supergateway, SSE deprecated), added per-environment YAML/examples (Holmes CLI, Holmes Helm Chart, Robusta Helm Chart) showing headers (extra_headers vs headers), llm_instructions, request_context and env-var templating, updated CLI/Helm commands placement, and added explicit migration warnings and notes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • arikalon1
  • moshemorad
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Simplify MCP servers documentation and improve clarity' accurately reflects the primary changes in the PR: reworking and simplifying MCP servers documentation with improved organization and practical examples.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Feb 4, 2026 •

Copy link
Copy Markdown
Contributor

🔬 CLI Performance Benchmark

🟡 Startup Time (no LLM)

Measures holmes version execution time (imports + initialization)

Metric PR Master Change
Cold Start 10.77s 10.78s -0.1%
Warm Mean 5.17s 4.97s +3.9%
Warm Min 5.06s 4.95s
Warm Max 5.28s 5.02s

🟡 Full CLI with LLM

Measures holmes ask execution time (OpenRouter + Haiku 4.5)

Metric PR Master Change
Cold Start 31.16s 24.71s +26.1%
Warm Mean 8.44s 8.07s +4.5%
Warm Min 8.27s 7.91s
Warm Max 8.62s 8.24s

PR: 56c94b2b | Master: db3da9cc | Iterations: 5

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@docs/data-sources/remote-mcp-servers.md`:
- Around line 372-374: Replace the literal placeholder "your-auth-token-here" in
the example curl header with an environment variable placeholder to avoid
secret-scanner hits; update the X-Auth-Token header in the curl example (the
POST to /api/investigate) to use $AUTH_TOKEN (e.g., -H "X-Auth-Token:
$AUTH_TOKEN") so callers know to export the token into AUTH_TOKEN before running
the curl command.
- Around line 371-375: The markdown snippet uses a fenced code block but
markdownlint expects an indented code block (MD046); replace the fenced block
containing the curl example with an indented block by removing the triple
backticks and indenting each line by four spaces so the curl command and its
flags (the lines starting with curl -X POST and the -H/-d flags) become an
indented code block matching the repository's configured style.

Comment thread docs/data-sources/remote-mcp-servers.md
Comment thread docs/data-sources/remote-mcp-servers.md
Allows users to override the MCP server command at deploy time
without rebuilding the Docker image.

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n
Signed-off-by: Claude <noreply@anthropic.com>
mcp_servers is a top-level key in Helm values, not nested under
custom_toolsets. Fixed all Helm chart examples:
- Holmes Helm: mcp_servers at root level
- Robusta Helm: holmes.mcp_servers (not holmes.custom_toolsets.mcp_servers)

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n
Signed-off-by: Claude <noreply@anthropic.com>
- Use Dynatrace as example for streamable-http (observability platform)
- Use ticket database as example for stdio (internal tool)
- Use legacy analytics as example for SSE
- Use customer data API for dynamic headers example
- Add comment explaining what llm_instructions is for
- Update example commands to match the example servers

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n
Signed-off-by: Claude <noreply@anthropic.com>

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/data-sources/remote-mcp-servers.md`:
- Around line 292-301: The YAML has mis-indented llm_instructions under config;
move the llm_instructions key for my_mcp_server so it is at the same indentation
level as description and config (i.e., sibling keys of description and config
under my_mcp_server within holmes.mcp_servers), ensuring llm_instructions
appears directly under my_mcp_server and not nested inside config.
🧹 Nitpick comments (1)
docs/data-sources/remote-mcp-servers.md (1)

7-9: Add blank line before the list.

Per coding guidelines, add a blank line between the introductory text and the numbered list to ensure proper MkDocs rendering.

📝 Suggested change
 HolmesGPT supports three MCP transport modes:
+
 1. **`streamable-http`** (Recommended): Modern HTTP-based transport. Use this for new integrations.

As per coding guidelines: Add blank line between header/bold text and lists in MkDocs markdown to ensure proper rendering.

Comment thread docs/data-sources/remote-mcp-servers.md
mainred
mainred previously approved these changes Feb 5, 2026

@mainred mainred left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Went through the preview doc https://deploy-preview-1480--holmes-docs.netlify.app/data-sources/remote-mcp-servers/#configuration-format-migration

It looks great, the doc is neat but informative.

- Fixed Stdio section: use ticket_db consistently, fixed llm_instructions indent
- Fixed SSE section: use legacy_analytics with proper description
- Fixed Advanced section: use customer_data consistently across tabs

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n
Signed-off-by: Claude <noreply@anthropic.com>
Remove -t custom_toolset.yaml pattern from CLI examples. Show config
added directly to ~/.holmes/config.yaml which is the standard approach.

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n
Signed-off-by: Claude <noreply@anthropic.com>

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@docs/data-sources/remote-mcp-servers.md`:
- Around line 197-205: The examples under mcp_servers -> ticket_db use the
deprecated SSE transport (mode: sse and /sse URL); update those examples to set
mode: streamable-http and change the endpoint path to the
streamable-http-compatible path (replace the /sse path with the appropriate HTTP
streaming endpoint) so the ticket_db config and its llm_instructions reflect the
recommended streamable-http transport.
- Around line 363-367: The Dynatrace examples currently use the YAML key
"headers" with Jinja2 templates (e.g. "{{ env.DYNATRACE_API_KEY }}"), but
templates are only rendered for "extra_headers"; update those examples to move
the templated header entries from "headers" into "extra_headers" (or
alternatively replace the templated values with hard-coded strings if dynamic
rendering is not required). Locate the Dynatrace example blocks that reference
the env template and replace the "headers:" mapping with "extra_headers:"
preserving the same header names (e.g. Authorization or X-Auth-Token) and
templated values so the template engine will process them. Ensure any
non-templated, static header examples can remain under "headers" if you choose
the hard-coded approach.

Comment thread docs/data-sources/remote-mcp-servers.md
Comment thread docs/data-sources/remote-mcp-servers.md
@aantn

aantn commented Feb 8, 2026

Copy link
Copy Markdown
Collaborator Author

Went through the preview doc https://deploy-preview-1480--holmes-docs.netlify.app/data-sources/remote-mcp-servers/#configuration-format-migration

It looks great, the doc is neat but informative.

Thank you!

Conflict resolution:
- Master added new `icon_url` field for UI display in MCP server config
- Our branch had improved Dynatrace example with realistic llm_instructions
- Resolution: Keep our improved examples, add icon_url field to all examples

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/data-sources/remote-mcp-servers.md`:
- Line 397: The docs currently imply template syntax (e.g., {{ env.MY_VAR }} or
{{ request_context.headers['token'] }}) can be used in headers; update the text
to explicitly state that template interpolation is supported only in the
extra_headers field (not in headers), and update the Dynatrace examples that use
templates in headers (the examples referencing request_context.headers and env
variables) to instead show usage under extra_headers so readers get a correct,
working pattern.

Comment thread docs/data-sources/remote-mcp-servers.md
@aantn
aantn enabled auto-merge (squash) February 9, 2026 15:12
@aantn
aantn disabled auto-merge February 9, 2026 15:13
@RoiGlinik
RoiGlinik enabled auto-merge (squash) February 9, 2026 16:41
@RoiGlinik
RoiGlinik merged commit bee28de into master Feb 9, 2026
19 of 20 checks passed
@RoiGlinik
RoiGlinik deleted the claude/improve-mcp-docs-nJ4Le branch February 9, 2026 16:41
moshemorad pushed a commit that referenced this pull request Feb 22, 2026
## Summary
Significantly streamlined and reorganized the MCP servers documentation
to improve clarity and reduce verbosity. The documentation now focuses
on practical examples for different deployment scenarios while removing
redundant explanations and overly detailed background information.

## Key Changes

- **Condensed transport mode descriptions**: Reduced verbose
explanations to concise, actionable summaries for each transport mode
(streamable-http, stdio, sse)

- **Reorganized examples by deployment context**: Restructured
documentation using tabs to show Holmes CLI, Holmes Helm Chart, and
Robusta Helm Chart examples side-by-side, making it easier for users to
find relevant configurations

- **Simplified streamable-http section**: Removed lengthy configuration
structure explanation and consolidated into practical deployment
examples with environment variable usage

- **Streamlined stdio documentation**:
  - Removed redundant warnings about limitations
  - Consolidated Supergateway setup instructions
  - Simplified Docker and Kubernetes examples
  - Removed verbose comments and placeholder text

- **Removed Supergateway demo section**: Eliminated the dedicated
"Working with Stdio MCP Servers via Supergateway" section and integrated
essential information into the stdio section itself

- **Condensed SSE section**: Reduced deprecated SSE documentation to
minimal guidance with tab-based examples

- **Reorganized advanced configuration**: Moved dynamic headers
documentation to a dedicated "Advanced Configuration" section with
clearer examples

- **Simplified migration notes**: Reduced configuration format change
documentation to essential information only

## Notable Details

- Removed ~50 lines of redundant explanations and background information
- Improved consistency in example formatting across all deployment
scenarios
- Maintained all essential technical information while improving
readability
- Reduced overall documentation length by ~25% while improving usability

https://claude.ai/code/session_01H3xyWcwWem2ptcZjFaNs8n

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Reorganized remote MCP server docs into per-environment guides (Holmes
CLI, Holmes Helm Chart, Robusta Helm Chart) with concrete YAML examples
and environment-scoped commands.
* Standardized transport guidance: promoted Streamable‑HTTP, emphasized
in-cluster stdio via Supergateway, and deprecated SSE.
* Moved URL/path guidance into per-server blocks, added llm_instructions
and header templating examples, and included migration notes with
compatibility warnings.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Roi Glinik <groi.tech@gmail.com>
Signed-off-by: Mohse Morad <moshemorad12340@gmail.com>
@coderabbitai coderabbitai Bot mentioned this pull request Mar 5, 2026
@coderabbitai coderabbitai Bot mentioned this pull request Mar 16, 2026
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.

4 participants