Add weekly update for 2026-04-27

[Derek2Tu]

Description

Adds the 2026-04-27 weekly update post covering:

• Local vMCP via the CLI — links to the new thv vmcp guide and frames who the local mode is for (evaluation, local dev against several MCP servers, lighter tool lists via the optimizer).
• Skills installation in ToolHive Desktop UI v0.32.2 — install skills directly into Claude Code, Cursor, and other ToolHive-managed clients; 130 skills in the bundled registry; connect a custom registry; package your own skills.
• Registry Server version metadata — ListRegistryEntries now embeds version metadata in list responses, replacing an N+1 fetch pattern.

Drops items already covered in the 2026-04-20 post (claims endpoint, dropped legacy format, single managed source, DB password, claims required on publish) and skips API cleanup, fixes, and security/under-the-hood items per editorial scope for this week.

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs-website	Ready	Preview, Comment	Apr 28, 2026 6:05pm

[danbarr]

@claude perform an editorial review of this PR; keep in mind it's an update blog post not a docs page.

[claude]

Claude finished @danbarr's task in 1m 17s —— View job

---

Editorial review

• Read the PR file
• Analyze content, tone, and style
• Post review feedback

---

Overall this is a solid, well-structured update post. The intro paragraph does a good job summarizing all three topics, the {/* truncate */} is placed correctly, and the post avoids em dashes and smart quotes. A few things worth addressing before merge:

Issues to fix

1. UI element not bolded — Skills tab (line 37)

"ToolHive Desktop UI v0.32.2 makes the Skills tab the place to discover..."

Per the style guide, UI elements should be in bold. Should read: Skills tab.

Fix this →

2. Title/content order mismatch

The title is "Discover and install skills in your AI client, and run vMCP locally" — skills first, vMCP second — but the post covers vMCP first and skills second. Readers scanning the title will expect to hit skills content first and may feel disoriented. Either reorder the title to "Run vMCP locally and install skills into your AI client" to match the post body, or swap the section order. The vMCP-first ordering makes sense given it's the bigger structural change.

Fix this →

3. Awkward phrasing — "turning catalog pages into an N+1 query pattern" (line 58)

"...turning catalog pages into an N+1 query pattern."

"Catalog pages" is an odd framing — it's more natural to say something like "...turning every catalog view into an N+1 query pattern." The N+1 terminology is fine for the technical audience, but "catalog pages" reads as a mixed metaphor (pages is a UI concept, N+1 is an API concept).

Fix this →

Suggestions (optional)

4. Tone shift in the third section

The first two sections speak directly to what users can do ("you can take the MCP servers you already run," "Pick a skill and install it"). The registry version metadata section shifts to describing system behavior ("UIs and registry clients can render staleness signals...") without framing what the reader can now do as a result. Consider adding a lead sentence from the user's perspective, e.g.: "If you build on top of the Registry Server, or use a client that does, you'll notice a speed improvement and richer catalog views."

5. Brief definition of "skills" would help new readers

"Skills" is mentioned six times in the second section but never defined in the post itself. The link to /toolhive/concepts/skills covers it, but a one-liner in the intro to that section would serve readers who are new to the term — e.g., "skills are reusable prompt bundles for your AI client."

6. Consider "we" voice per blog post conventions

The style guide explicitly permits first-person voice in update posts. The current post uses impersonal framing throughout ("Virtual MCP Server is now supported locally," "ToolHive Desktop UI v0.32.2 makes the Skills tab..."). Switching some lines to "we've" or "we're" would bring it closer to the voice of a team-written update and differentiate it more clearly from docs. This is low-priority but worth a pass if the post feels too formal.

[Copilot]

Pull request overview

Adds the weekly ToolHive updates post for 2026-04-27, summarizing new local vMCP CLI support, Desktop UI skill installation, and Registry Server list responses including version metadata.

Changes:

• Adds a new weekly update MDX post for Apr 27 covering vMCP local mode, skills installation in Desktop UI v0.32.2, and registry version metadata in list responses.
• Links readers to the relevant ToolHive guides and release pages for follow-up details.

[Copilot]

The lead sentence is a comma splice (multiple independent clauses joined by commas), which reads as a run-on. Consider splitting into two sentences or using a semicolon/em-dash after “locally” to improve grammar and readability.

Suggested change

	This week, Virtual MCP Server (vMCP) is now supported locally, the ToolHive
	Desktop UI installs skills directly into the AI clients you already use, and the
	Registry Server surfaces version information in list views.
	This week, Virtual MCP Server (vMCP) is now supported locally, and the ToolHive
	Desktop UI installs skills directly into the AI clients you already use. The
	Registry Server also surfaces version information in list views.

[Copilot]

“This applies to both MCP server and skill entries …” is slightly ambiguous/uneven phrasing (singular vs plural) and can read like it applies to an MCP server plus multiple skills. Consider rewording to “both MCP server entries and skill entries” (or similar) for clarity.

Suggested change

	response. This applies to both MCP server and skill entries served through the
	registry-scoped browse endpoints.
	response. This applies to both MCP server entries and skill entries served
	through the registry-scoped browse endpoints.

[Derek2Tu]

Addressed in 0b73334 (preceded by 4d196c7 which reordered sections to lead with skills and bumped Desktop UI to v0.33.0).

From @copilot-pull-request-reviewer:

• ✅ Comma-spliced lede → split into two sentences.
• ✅ "both MCP server and skill entries" → "both MCP server entries and skill entries".

From the @claude editorial review:

• ✅ Skills tab should be bold — section was rewritten; the tab names (Registry, Local Builds, Installed) are now bolded inline.
• ✅ Title/content order mismatch — sections reordered so skills leads, matching the title.
• ✅ "turning catalog pages into an N+1 query pattern" → "turning every list view into an N+1 fetch pattern".
• ✅ Registry-metadata section now opens with a user-facing lead ("If you build a UI on top of the Registry Server…").
• ✅ Added a one-line skills definition at the top of the skills section for new readers.
• ⏭️ Skipped: "we" voice. The post reads consistently in second person; happy to revisit if you'd prefer a team-voice rewrite.

Heads-up on broken-link CI: The four new /toolhive/guides-ui/skills* links resolve to pages added in #813. CI builds on this branch will fail the broken-link check until #813 lands. Recommend merging #813 first.

[claude]

Claude finished @Derek2Tu's task in 1m 0s —— View job

---

Follow-up review

• Read the updated file
• Verify each reported fix
• Post follow-up review

---

All reported fixes check out. Here's the verification:

From @copilot-pull-request-reviewer:

• ✅ Comma-spliced lede → now two clean sentences: "This week, the ToolHive Desktop UI installs skills directly into the AI clients you already use, and Virtual MCP Server (vMCP) is now supported locally. The Registry Server also surfaces version information in list views."
• ✅ "both MCP server entries and skill entries" (line 74–75) → confirmed.

From the previous @claude editorial review:

• ✅ UI element bolding → Registry, Local Builds, and Installed tabs all bolded inline (line 21).
• ✅ Title/content order → skills section leads (line 16), matching the title. vMCP follows (line 46).
• ✅ N+1 phrasing → "turning every list view into an N+1 fetch pattern" (line 71–72).
• ✅ User-facing lead on registry section → "If you build a UI on top of the Registry Server, or use a client that does, catalog views now load faster…" (line 67–68).
• ✅ Skills definition → "Skills are reusable instruction bundles that teach AI clients how to perform specific tasks." (line 18).
• ⏭️ "We" voice skipped — second-person voice is consistent throughout; no issue.

No new issues found. The post reads cleanly and is ready to merge once #813 lands to resolve the broken-link check on the /toolhive/guides-ui/skills* links.