Skip to content

Release v22.177.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 03:42
1db86d4

Summary

Arc can now serve MCP from the capabilities endpoint group through a new, strictly opt-in Cratis.Arc.Mcp package. Nothing is exposed unless it is declared, and the core packages do not reference the package or the MCP SDK.

Added

  • Cratis.Arc.Mcp package: enable with WithMcp() and MapCratisArcMcp(); commands and queries are served only when marked [ExposeOverMcp] or declared through McpBuilder.Expose<T>() / ExposeQuery; custom tools plug in through IMcpToolSource (#3712).
  • Protected resource metadata, 401 challenges, and credential-kind profiles (PatOnly, OAuthOnly, Combined) with scope ceilings, alternative scope sets, and McpOptions.ReadScope / WriteScope / WriteScopes (#3712).
  • IMcpToolAuthorizer to narrow access per tool, distinguishing listing from calling; McpRefusals so host middleware can write Arc-shaped refusals (#3712).
  • Origin allow-list, public-origin configuration, and fail-closed startup validation (#3712).
  • MCP documentation covering setup, scopes, authorizers, and hosting on a capability port (#3712).

Changed

  • Capability gates can admit an endpoint that accepts both personal access tokens and verified OAuth credentials through server-owned endpoint metadata; other gated endpoints stay PAT-only.
  • Arc and Arc.Core no longer expose internals to the MCP package; the seams it needs are small public extension points.