Skip to content

Add weekly update for 2026-05-11#864

Open
Derek2Tu wants to merge 3 commits into
mainfrom
weekly-updates-2026-05-11
Open

Add weekly update for 2026-05-11#864
Derek2Tu wants to merge 3 commits into
mainfrom
weekly-updates-2026-05-11

Conversation

@Derek2Tu
Copy link
Copy Markdown
Contributor

Description

Adds the 2026-05-11 weekly update post covering:

  • Redis topology support for the embedded auth server. The MCPExternalAuthConfig resource now accepts Redis standalone and Redis Cluster alongside the existing Sentinel option, so operators can match the Redis deployment their platform already runs.
  • Client ID Metadata Document (CIMD) support in the thv CLI. The CLI can present a hosted metadata document to upstream IdPs instead of going through dynamic client registration, avoiding stale client entries from short-lived MCP clients. Embedded authorization server support is still in development; this release lands CIMD in the local CLI experience first.

Type of change

  • Documentation update

Submitter checklist

Content and formatting

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

🤖 Generated with Claude Code

Cover Redis topology support (standalone, cluster, Sentinel) for the
embedded auth server's session storage, and Client ID Metadata Document
(CIMD) support landing in the ToolHive CLI ahead of the embedded
authorization server rollout.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 11, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment May 11, 2026 5:45pm

Request Review

Lead both sections with the user pain point and value: pluggable Redis
topologies for platforms that don't run Sentinel, and dropping dynamic
client registration churn via CIMD in the CLI. Reorder the title and
description to match.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Update page title and section H2s to consistent product-focused wording:
"Plug ToolHive into your existing Redis setup" and "ToolHive CLI now
supports CIMD".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@@ -0,0 +1,65 @@
---
title: Plug ToolHive into your existing Redis setup, and CIMD in the CLI
sidebar_label: 'May 11: Existing Redis and CIMD in the CLI'
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.

Suggested change
sidebar_label: 'May 11: Existing Redis and CIMD in the CLI'
sidebar_label: 'May 11: Redis flexibility and CIMD in the CLI'

I think "Redis flexibility" is more accurate? AFAIK it was always an existing Redis, we just have more flexibility around your specific topology?

Comment on lines +21 to +25
- **Standalone Redis** for simpler operations when high availability isn't a
hard requirement.
- **Redis Cluster** for sharded scale-out across multiple nodes.
- **Redis Sentinel** for HA with automatic failover (still the recommended
default for production).
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.

@reyortiz3 is this still the correct framing? Aren't the other modes a match for managed Redis where the provider is handling the HA? This implies they're not suitable for production.

[Redis session storage](/toolhive/guides-k8s/redis-session-storage#configure-mcpexternalauthconfig)
for the YAML and TLS examples.

## ToolHive CLI now supports CIMD
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.

Should this section mention the fact that CIMD is preferred over DCR now in the MCP spec (DCR isn't even mentioned here)? Shows we're keeping up with upstream changes?

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