Skip to content

0.7 mcp gateway post#93

Merged
jasonmadigan merged 1 commit into
mainfrom
mcp-gateway-0.7-blog
Jun 3, 2026
Merged

0.7 mcp gateway post#93
jasonmadigan merged 1 commit into
mainfrom
mcp-gateway-0.7-blog

Conversation

@david-martin

@david-martin david-martin commented Jun 3, 2026

Copy link
Copy Markdown
Member

docs links depend on Kuadrant/docs.kuadrant.io#244

Summary by CodeRabbit

  • Documentation
    • Announced MCP Gateway 0.7 release with new capabilities: tool discovery, per-user tool listings, prompt federation, and OAuth resource configuration.
    • Documented security improvements and breaking changes with migration guidance.

@netlify

netlify Bot commented Jun 3, 2026

Copy link
Copy Markdown

Deploy Preview for relaxed-faloodeh-7fa6f1 ready!

Name Link
🔨 Latest commit bef14ba
🔍 Latest deploy log https://app.netlify.com/projects/relaxed-faloodeh-7fa6f1/deploys/6a204808152d2800083b00d2
😎 Deploy Preview https://deploy-preview-93--relaxed-faloodeh-7fa6f1.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.

@coderabbitai

coderabbitai Bot commented Jun 3, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@david-martin, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 59 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 65531dab-ee40-42a6-a2c0-3dca4afb9dd7

📥 Commits

Reviewing files that changed from the base of the PR and between 999e939 and bef14ba.

📒 Files selected for processing (1)
  • src/blog/mcp-gateway-0.7/mcp-gateway-0.7.md
📝 Walkthrough

Walkthrough

This pull request adds a blog post announcing the MCP Gateway 0.7 release dated 3 June 2026. The post documents new capabilities including tool discovery, per-user tool listings, prompt federation, OAuth protected resources via CRD, and server state control. It lists breaking changes and provides links to migration guides and community resources.

Changes

Release Announcement

Layer / File(s) Summary
Blog post content
src/blog/mcp-gateway-0.7/mcp-gateway-0.7.md
Markdown blog post announcing MCP Gateway 0.7, authored by David Martin. Documents new features (progressive meta-tools for discovery, per-user tool listings, prompt federation, OAuth CRD support, state field for enabling/disabling), breaking changes with migration paths, and links to release notes, 0.8 milestone, and community involvement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • maleck13
  • jasonmadigan

Poem

🐰 A gateway release hops into view,
With tools that discover and prompts anew,
Breaking changes noted, the migration's clear,
MCP Gateway 0.7 is finally here!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'MCP Gateway 0.7 post' directly refers to the blog post file being added and accurately reflects the main change—announcing the MCP Gateway 0.7 release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch mcp-gateway-0.7-blog

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.

@david-martin david-martin marked this pull request as ready for review June 3, 2026 13:44
jasonmadigan
jasonmadigan previously approved these changes Jun 3, 2026
@david-martin

Copy link
Copy Markdown
Member Author

Thanks @jasonmadigan would you mind another approve.
I pushed up a yaml fix in the examples for targetRef.

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

🧹 Nitpick comments (1)
src/blog/mcp-gateway-0.7/mcp-gateway-0.7.md (1)

17-17: 💤 Low value

Consider adding comma before 'so'.

The sentence connects two independent clauses. Adding a comma before "so" would improve readability: "...notifications/tools/list_changed event, so the agent refreshes its view."

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/blog/mcp-gateway-0.7/mcp-gateway-0.7.md` at line 17, Edit the sentence
describing discover_tools/select_tools to add a comma before "so" for clarity:
update the line that mentions `discover_tools` and `select_tools` and the
`notifications/tools/list_changed` event to read "...sending a
`notifications/tools/list_changed` event, so the agent refreshes its view."
Ensure the change is applied where the phrase mentioning `discover_tools`,
`select_tools`, and `notifications/tools/list_changed` appears.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/blog/mcp-gateway-0.7/mcp-gateway-0.7.md`:
- Line 17: Edit the sentence describing discover_tools/select_tools to add a
comma before "so" for clarity: update the line that mentions `discover_tools`
and `select_tools` and the `notifications/tools/list_changed` event to read
"...sending a `notifications/tools/list_changed` event, so the agent refreshes
its view." Ensure the change is applied where the phrase mentioning
`discover_tools`, `select_tools`, and `notifications/tools/list_changed`
appears.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 435ea107-3e43-4d79-9416-3f4382651ad4

📥 Commits

Reviewing files that changed from the base of the PR and between 843dd8e and 999e939.

📒 Files selected for processing (1)
  • src/blog/mcp-gateway-0.7/mcp-gateway-0.7.md

@Patryk-Stefanski

Copy link
Copy Markdown

@david-martin I don't see these breaking changes mentioned

  • --enforce-tool-filtering renamed to --enforce-capability-filtering
  • Keycloak roles now require tool: prefix

Signed-off-by: David Martin <davmarti@redhat.com>
@david-martin david-martin force-pushed the mcp-gateway-0.7-blog branch from 999e939 to bef14ba Compare June 3, 2026 15:28
@jasonmadigan jasonmadigan added this pull request to the merge queue Jun 3, 2026
Merged via the queue into main with commit 5cdecc6 Jun 3, 2026
7 checks passed
@github-project-automation github-project-automation Bot moved this to Done in Kuadrant Jun 3, 2026
@jasonmadigan jasonmadigan deleted the mcp-gateway-0.7-blog branch June 3, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants