Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Rework section structure to use ## headers with bold lead-in bullet points, remove version number from title, add product doc links, and consolidate Registry Server subsections. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
| for list endpoints that previously returned incomplete pages when access control | ||
| filtering removed rows. | ||
|
|
||
| ## Kubernetes Operator: Token-bucket rate limiting |
There was a problem hiding this comment.
nit: It doesn't really make sense to say "Kubernetes Operator" in this context. It would be more correct to say the "MCPServer in K8s support rate limiting"
| ## Kubernetes Operator: Token-bucket rate limiting | ||
|
|
||
| The [Kubernetes Operator](/toolhive/guides-k8s/) now supports | ||
| [token-bucket rate limiting](/toolhive/guides-k8s/rate-limiting) to prevent |
There was a problem hiding this comment.
nit: "token bucket" is an implementation detail. I would lead with "per-user, per-tool call rate limiting"
- Replace "ToolHive Studio" with "ToolHive desktop UI" throughout - Remove MCP Optimizer mention (deprecated/removed in UI) - Remove Sentry tracing and duplicate MCP Apps from under-the-hood - Add "and skill" to per-entry access control for K8s sources - Rename K8s section to "Per-user, per-tool call rate limiting" - Rephrase to use "MCPServers in Kubernetes" instead of "Kubernetes Operator" Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Reframe vMCP section as a feature highlight, not a docs update - Add use cases for rate limiting: resource exhaustion, performance degradation, and data exfiltration Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The post is in good shape overall — benefit-first framing throughout, clear technical language, no overselling. A few issues worth fixing: 1. Description and title omit vMCPThe description covers desktop UI, Registry Server, and Kubernetes but leaves out the vMCP embedded authorization server — which is one of the four main sections. Current description:
Suggested fix — add a vMCP clause, e.g.:
Similarly, the title lists three of the four stories but skips vMCP. Updating the description is more important; the title could optionally be broadened too (e.g., "Threaded chat, claim-based authorization, Kubernetes rate limiting, and embedded OAuth"). 2. Unexplained spec reference in the desktop UI section
This is unexplained jargon — most readers won't know what
3. Sidebar label covers only 2 of 4 topics
|
- Add vMCP to description and update sidebar label - Clarify mcp-apps spec reference with context - Broaden sidebar label to cover more topics Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
4 participants
Summary
/mecaller identity endpoint, skills sync from external sources, SIEM-compliant audit logging (merged, not yet released), immediate filter re-sync, fixed incomplete list paginationTest plan
/toolhive/guides-k8s/rate-limiting,/toolhive/guides-vmcp/authentication#embedded-authorization-server)🤖 Generated with Claude Code