Skip to content

chore(repo): version packages - #324

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore(repo): version packages#324
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

nitro-mcp-toolkit@0.3.0

Minor Changes

  • #323 936679e Thanks @HugoRCD! - The runtime is now h3-mcp 0.2.0. defineMcp* still wrap plain returns and turn a throw into isError; transport, eras, auth, origin, MRTR, and subscriptions come from the engine.

    This is a breaking change on 0.x:

    • ResourceTemplate / completable are gone. A template is uriTemplate plus optional list / complete; prompt completions live on arguments.
    • inputRequired / mcpElicit / getElicitedContent / defineRequestState replace inputResponse / acceptedContent.
    • legacy / responseMode become era (dual is the default, modern is 2026-07-28 only).
    • event.context.mcp.mcpReq / auth are gone. Read inputResponses, requestState, signal, and era off the engine context.
    • handler.fetch(req, { authInfo }) is gone; send Authorization or x-api-key.
    • handler.bus / handler.close are gone. handler.notify still fans out to every listener.
    • Cloudflare no longer needs nodejs_compat.
    • An X-MCP-Tools header naming an unknown tool is a 400 only after origin and auth have passed, so the name does not leak to a caller who is not allowed through.
    • createMcpHandler takes h3-mcp's { extensionPlugins } as a second argument, for tasks and MCP Apps.
    • Engine types (AuthOptions, CacheHints, CallToolResult, Era, PluginOptions, …) keep their h3-mcp names.
    • getInputResponses / getMissingInputs / canRequestInput / getSupportedInputs / McpJsonRpcError are re-exported so a handler does not need a second import from h3-mcp.
    • nitro is an optional peer: it is only required for nitro-mcp-toolkit/module. createMcpHandler needs h3.
    • createMcpTestClient accepts { headers } so a Bearer token or X-MCP-Tools allowlist does not need a custom fetch wrap.
    • Import a mounted handler as { mcp } (or { adminMcp } for /admin/mcp) from nitro-mcp-toolkit/servers. #mcp/<slug>/handler is still what Nitro mounts, not what an app imports.

@vercel

vercel Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
nuxt-mcp-toolkit-docs Ready Ready Preview Aug 19, 2026 3:33pm

Request Review

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.

0 participants