feat(ai-mcp): forward MCP tool annotations and titles - #1031
Merged
AlemTuzlak merged 3 commits intoAug 7, 2026
Conversation
Discovery previously stamped only serverToolName/serverId/uiResourceUri onto `metadata.mcp`, dropping the server's `annotations` hints and `title` from tools/list — so a host could only ever see a tool's name and description. Forward both, on the auto-discovery AND explicit `tools([...defs])` paths, via a shared `toolMcpMetadata()` so the two cannot drift: - `annotations` — the server's object verbatim (readOnlyHint, destructiveHint, idempotentHint, openWorldHint, annotations.title), omitted when absent so the explicit path's merge can't blank out caller-supplied metadata. - `title` — display name resolved with the spec's precedence: `title` -> `annotations.title` -> `name`. Titles are display-only: the model-facing tool name and prefixing are unchanged, and nothing new is sent to providers. Also exports `McpToolMetadata` (the full `metadata.mcp` shape — `metadata` is `Record<string, any>`, so this is what makes reads typed without a cast) and re-exports the SDK's `ToolAnnotations`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
suryaashish-kubesense
changed the title
suryaashish-kubesense
marked this pull request as ready for review
July 31, 2026 06:47
suryaashish-kubesense
changed the title
Contributor
📝 WalkthroughWalkthroughMCP tool metadata now includes resolved display titles, annotations, server identity, and UI resource URIs. The metadata supports auto-discovered and explicitly bound tools, package exports, documentation, and unit and E2E validation. ChangesMCP tool metadata
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant MCPServer
participant MCPClientImpl
participant toolMcpMetadata
participant ToolCatalog
MCPServer->>MCPClientImpl: expose tool definition
MCPClientImpl->>toolMcpMetadata: resolve MCP metadata
toolMcpMetadata-->>MCPClientImpl: return title and annotations
MCPClientImpl-->>ToolCatalog: expose metadata.mcp
ToolCatalog->>ToolCatalog: render title and read/write status
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
suryaashish-kubesense
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
packages/ai-mcp/src/types.ts (1)
24-42: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winMake guaranteed metadata fields required.
toolMcpMetadataalways setsserverToolNameandtitle. The interface marks both fields as optional. Make these fields required so consumers can use the documented contract without redundant fallback handling.Proposed fix
- serverToolName?: string + serverToolName: string ... - title?: string + title: string🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/ai-mcp/src/types.ts` around lines 24 - 42, Update the McpToolMetadata interface to make serverToolName and title required properties, matching the guarantees provided by toolMcpMetadata. Leave serverId, uiResourceUri, and annotations optional.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/tools/mcp.md`:
- Around line 296-303: Update the tools mapping around mcp.tools() so
readOnlyHint cannot by itself set needsApproval to false; require an
independently established trusted-server condition before bypassing approval,
while retaining the hint for labels or recommendations. Revise the adjacent
warning to explicitly state that annotations are advisory and must not serve as
the security boundary for untrusted servers.
- Around line 319-321: Validate that process.env.MCP_URL is present before the
createMCPClient call, returning a clear response when it is absent. Store the
validated value and pass it to the HTTP transport instead of using the non-null
assertion, ensuring resolveTransport receives a defined URL.
- Around line 292-294: Update the one-shot MCP client example around
createMCPClient to use scoped async disposal with await using, ensuring the
client transport closes automatically after tool discovery. Preserve the
existing HTTP transport configuration and read flow.
In `@packages/ai-mcp/tests/tools.test.ts`:
- Around line 257-316: Move the toServerTools coverage from
packages/ai-mcp/tests/tools.test.ts lines 257-316 into
packages/ai-mcp/src/tools.test.ts, preserving the existing tests. Also move the
MCPClientImpl.tools coverage from packages/ai-mcp/tests/client.test.ts lines
118-150 into packages/ai-mcp/src/client.test.ts; no other test behavior should
change.
---
Nitpick comments:
In `@packages/ai-mcp/src/types.ts`:
- Around line 24-42: Update the McpToolMetadata interface to make serverToolName
and title required properties, matching the guarantees provided by
toolMcpMetadata. Leave serverId, uiResourceUri, and annotations optional.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 249bc044-c1eb-438e-b0af-a04be2ba0763
📒 Files selected for processing (13)
.changeset/mcp-tool-annotations.mddocs/config.jsondocs/tools/mcp.mdpackages/ai-mcp/src/client.tspackages/ai-mcp/src/index.tspackages/ai-mcp/src/tools.tspackages/ai-mcp/src/types.tspackages/ai-mcp/tests/client.test.tspackages/ai-mcp/tests/helpers/in-memory-server.tspackages/ai-mcp/tests/tools.test.tstesting/e2e/src/routes/api.mcp-server.tstesting/e2e/src/routes/api.mcp-status-test.tstesting/e2e/tests/mcp-status.spec.ts
Comment on lines
+292
to
+294
| const mcp = await createMCPClient({ | ||
| transport: { type: 'http', url: 'https://my-mcp-server.example.com/mcp' }, | ||
| }) |
Contributor
There was a problem hiding this comment.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Expect this one-shot example to use `await using` or explicit cleanup.
rg -n -C 4 '\bcreateMCPClient\b|await using|\.close\(' docs packages/ai-mcpRepository: TanStack/ai
Length of output: 50370
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Locate and inspect the documented example and nearby lifecycle wording.
if [ -f docs/tools/mcp.md ]; then
echo '--- docs/tools/mcp.md around createMCPClient example ---'
sed -n '274,310p' docs/tools/mcp.md | cat -n
else
echo 'docs/tools/mcp.md not found'
fi
echo '--- createMCPClients examples without close/await using (grep only) ---'
rg -n -C 3 'createMCPClients\b' docs/tools/mcp.md packages/ai-mcp/skills/ai-mcp/SKILL.md | sed -n '1,120p'Repository: TanStack/ai
Length of output: 9684
Dispose the MCP client in this one-shot example.
This example creates the client and reads tools, but does not close the transport. Use await using mpc = await createMCPClient(...) for this one-shot read, or document explicit cleanup after tool discovery.
Suggested cleanup
-const mcp = await createMCPClient({
+await using mcp = await createMCPClient({📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| const mcp = await createMCPClient({ | |
| transport: { type: 'http', url: 'https://my-mcp-server.example.com/mcp' }, | |
| }) | |
| await using mcp = await createMCPClient({ | |
| transport: { type: 'http', url: 'https://my-mcp-server.example.com/mcp' }, | |
| }) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/tools/mcp.md` around lines 292 - 294, Update the one-shot MCP client
example around createMCPClient to use scoped async disposal with await using,
ensuring the client transport closes automatically after tool discovery.
Preserve the existing HTTP transport configuration and read flow.
Comment on lines
+319
to
+321
| await using mcp = await createMCPClient({ | ||
| transport: { type: 'http', url: process.env.MCP_URL! }, | ||
| }) |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Inspect project conventions for validating this environment variable.
rg -n -C 4 'process\.env\.MCP_URL|createMCPClient' docs packages/ai-mcpRepository: TanStack/ai
Length of output: 50370
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Target file context:"
fd '^mcp\.md$' docs -x sh -c 'wc -l "$1"; echo "--- $1"; sed -n "290,335p" "$1"' sh {}
echo
echo "Exact process.env.MCP_URL occurrences:"
rg -n -C 3 'process\.env\.MCP_URL|createMCPClient\(\{' docs packages/ai-mcp/skills/ai-mcp/SKILL.md packages/ai-mcp/README.md
echo
echo "Relevant client.ts signatures/top:"
fd '^client\.ts$' packages/ai-mcp/src -x sh -c 'wc -l "$1"; echo "--- $1"; sed -n "1,220p" "$1"' sh {} 2>/dev/null || true
echo
echo "HTTP transport URL behavior in MCP SDK references in repo:"
git ls-files | rg 'modelcontextprotocol|http-stream|streamable|stream-http|ClientTransport' | head -100Repository: TanStack/ai
Length of output: 33670
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "transport.ts:"
fd '^transport\.ts$' packages/ai-mcp/src -x sh -c 'wc -l "$1"; echo "--- $1"; cat -n "$1"' sh {}
echo
echo "TransportConfig definitions/usages in ai-mcp src:"
rg -n -C 3 'interface TransportConfig|type TransportConfig|resolveTransport|StreamableHTTPClientTransport|new URL|new StreamableHTTPClientTransport|new (StreamableHTTPClientTransport|SSEClientTransport|StdioClientTransport)' packages/ai-mcp/src
echo
echo "Lockfile SDK versions:"
rg -n '"(`@modelcontextprotocol/sdk`)|streamableHttp|SSEClientTransport|StdioClientTransport' package.json pnpm-lock.yaml package-lock.json npm-shrinkwrap.json yarn.lock 2>/dev/null | head -200 || true
echo
echo "Package deps:"
fd '^package\.json$' packages/ai-mcp -x sh -c 'echo "--- $1"; sed -n "1,120p" "$1"' sh {}Repository: TanStack/ai
Length of output: 10103
Validate MCP_URL before constructing the MCP client.
process.env.MCP_URL! only bypasses TypeScript checking. If the variable is missing, createMCPClient({ transport: { type: 'http', url: process.env.MCP_URL! } }) passes undefined to resolveTransport, and the HTTP transport constructor receives new URL(undefined), which throws before configuration validation. Return a clear response when MCP_URL is absent, then pass the validated URL.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/tools/mcp.md` around lines 319 - 321, Validate that process.env.MCP_URL
is present before the createMCPClient call, returning a clear response when it
is absent. Store the validated value and pass it to the HTTP transport instead
of using the non-null assertion, ensuring resolveTransport receives a defined
URL.
Source: Coding guidelines
Comment on lines
+257
to
+316
| describe('toServerTools — annotations + title', () => { | ||
| it('forwards the server annotations verbatim', () => { | ||
| const annotations = { | ||
| title: 'Weather Lookup', | ||
| readOnlyHint: true, | ||
| destructiveHint: false, | ||
| idempotentHint: true, | ||
| openWorldHint: true, | ||
| } | ||
| const tool = toServerTools( | ||
| fakeMcpClient(vi.fn()), | ||
| [mcpToolDef({ name: 'get_weather', description: 'w', annotations })], | ||
| {}, | ||
| )[0]! | ||
| expect(readToolMcpMeta(tool).annotations).toEqual(annotations) | ||
| }) | ||
|
|
||
| it('omits annotations entirely when the server declares none', () => { | ||
| const tool = toServerTools( | ||
| fakeMcpClient(vi.fn()), | ||
| [mcpToolDef({ name: 'get_weather' })], | ||
| {}, | ||
| )[0]! | ||
| const mcp = readToolMcpMeta(tool) | ||
| expect(mcp.annotations).toBeUndefined() | ||
| // Omitted, not present-with-undefined — the explicit tools(defs) path | ||
| // merges this block over caller-supplied metadata. | ||
| expect('annotations' in mcp).toBe(false) | ||
| }) | ||
|
|
||
| it('resolves title with MCP precedence: title > annotations.title > name', () => { | ||
| const [both, annotationsOnly, neither] = toServerTools( | ||
| fakeMcpClient(vi.fn()), | ||
| [ | ||
| mcpToolDef({ | ||
| name: 'a', | ||
| title: 'Top Level', | ||
| annotations: { title: 'Legacy' }, | ||
| }), | ||
| mcpToolDef({ name: 'b', annotations: { title: 'Legacy' } }), | ||
| mcpToolDef({ name: 'c' }), | ||
| ], | ||
| {}, | ||
| ) | ||
| expect(readToolMcpMeta(both!).title).toBe('Top Level') | ||
| expect(readToolMcpMeta(annotationsOnly!).title).toBe('Legacy') | ||
| expect(readToolMcpMeta(neither!).title).toBe('c') | ||
| }) | ||
|
|
||
| it('keeps the prefixed tool name independent of the display title', () => { | ||
| const tool = toServerTools( | ||
| fakeMcpClient(vi.fn()), | ||
| [mcpToolDef({ name: 'get_weather', title: 'Weather Lookup' })], | ||
| { prefix: 'wx' }, | ||
| )[0]! | ||
| // The title is display-only — it must never leak into the model-facing name. | ||
| expect(tool.name).toBe('wx_get_weather') | ||
| expect(readToolMcpMeta(tool).title).toBe('Weather Lookup') | ||
| }) | ||
| }) |
Contributor
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Place new unit coverage beside its source module.
The added unit tests are not colocated with their covered source modules.
packages/ai-mcp/tests/tools.test.ts#L257-L316: move thetoServerToolscoverage topackages/ai-mcp/src/tools.test.ts.packages/ai-mcp/tests/client.test.ts#L118-L150: move theMCPClientImpl.toolscoverage topackages/ai-mcp/src/client.test.ts.
📍 Affects 2 files
packages/ai-mcp/tests/tools.test.ts#L257-L316(this comment)packages/ai-mcp/tests/client.test.ts#L118-L150
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/ai-mcp/tests/tools.test.ts` around lines 257 - 316, Move the
toServerTools coverage from packages/ai-mcp/tests/tools.test.ts lines 257-316
into packages/ai-mcp/src/tools.test.ts, preserving the existing tests. Also move
the MCPClientImpl.tools coverage from packages/ai-mcp/tests/client.test.ts lines
118-150 into packages/ai-mcp/src/client.test.ts; no other test behavior should
change.
Source: Coding guidelines
The approval-gating sample keyed `needsApproval` off `readOnlyHint` alone, so a single server-supplied boolean could waive the confirmation step — a compromised server can claim `readOnlyHint: true` on a destructive tool. It also contradicted the warning directly beneath it. Gate on `!(serverIsTrusted && advertisedReadOnly)`, where trust comes from a caller-configured allowlist rather than anything on the wire, and rewrite the warning to say annotations are advisory and must never be the security boundary for an untrusted server — hints may relax a confirmation only on independently trusted servers, and are display labels everywhere else. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`ServerTool.metadata` is `Record<string, any> | undefined`, so `tool.metadata.mcp` did not compile and its fields were `any` — reading the forwarded MCP title/annotations needed a hand-written annotation that TS could not check. Every `tools()` path (single client, explicit `tools([...defs])`, and the `createMCPClients` pool) now returns `McpServerTool`s: structurally still `ServerTool`s, but with `metadata.mcp` statically present and typed as `McpToolMetadata`. So `tool.metadata.mcp.annotations?.readOnlyHint` infers on its own and a misspelled field is a compile error. - `McpToolMetadata.serverToolName` / `.title` are now required, since both are always stamped — no more fallback for a value that is never missing. - The explicit path rebuilds the bound tool instead of mutating it, because assigning `metadata` cannot narrow the declared type. - Docs, tests, and the e2e route drop their annotations and read straight through; new type-level tests cover all four paths plus the typo case.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/ai-mcp/src/types.ts`:
- Around line 20-22: Remove the readOnlyHint-based approval-bypass example from
the documentation comment in the MCP types definition. Replace it with guidance
that server-provided annotations may inform display only and must never bypass
approval or authorization.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 2ef97b8d-d8d6-4485-a784-f0a2fd18cc85
📒 Files selected for processing (11)
.changeset/mcp-tool-annotations.mddocs/tools/mcp.mdpackages/ai-mcp/src/client.tspackages/ai-mcp/src/index.tspackages/ai-mcp/src/pool.tspackages/ai-mcp/src/tools.tspackages/ai-mcp/src/types.tspackages/ai-mcp/tests/client.test.tspackages/ai-mcp/tests/tools.test.tspackages/ai-mcp/tests/types.test-d.tstesting/e2e/src/routes/api.mcp-status-test.ts
🚧 Files skipped from review as they are similar to previous changes (5)
- packages/ai-mcp/src/index.ts
- packages/ai-mcp/tests/tools.test.ts
- .changeset/mcp-tool-annotations.md
- docs/tools/mcp.md
- packages/ai-mcp/tests/client.test.ts
Comment on lines
+20
to
+22
| * if (tool.metadata.mcp.annotations?.readOnlyHint) { | ||
| * // e.g. skip the approval prompt for a read-only tool | ||
| * } |
Contributor
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Do not use readOnlyHint to bypass approval.
Lines 20-22 show a server-provided annotation as a reason to skip an approval prompt. A malicious or incorrect MCP server can set this hint and suppress user confirmation for a mutating tool. Remove this example. State that annotations can inform display only and must not bypass approval or authorization.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/ai-mcp/src/types.ts` around lines 20 - 22, Remove the
readOnlyHint-based approval-bypass example from the documentation comment in the
MCP types definition. Replace it with guidance that server-provided annotations
may inform display only and must never bypass approval or authorization.
AlemTuzlak
approved these changes
Aug 7, 2026
|
View your CI Pipeline Execution ↗ for commit fdc1754
☁️ Nx Cloud last updated this comment at |
@tanstack/ai
@tanstack/ai-acp
@tanstack/ai-angular
@tanstack/ai-anthropic
@tanstack/ai-bedrock
@tanstack/ai-byteplus
@tanstack/ai-claude-code
@tanstack/ai-client
@tanstack/ai-code-mode
@tanstack/ai-code-mode-skills
@tanstack/ai-codex
@tanstack/ai-devtools-core
@tanstack/ai-durable-stream
@tanstack/ai-elevenlabs
@tanstack/ai-event-client
@tanstack/ai-fal
@tanstack/ai-gemini
@tanstack/ai-grok
@tanstack/ai-grok-build
@tanstack/ai-groq
@tanstack/ai-isolate-cloudflare
@tanstack/ai-isolate-node
@tanstack/ai-isolate-quickjs
@tanstack/ai-isolate-quickjs-bun
@tanstack/ai-mcp
@tanstack/ai-memory
@tanstack/ai-mistral
@tanstack/ai-ollama
@tanstack/ai-openai
@tanstack/ai-opencode
@tanstack/ai-openrouter
@tanstack/ai-persistence
@tanstack/ai-preact
@tanstack/ai-react
@tanstack/ai-react-ui
@tanstack/ai-sandbox
@tanstack/ai-sandbox-cloudflare
@tanstack/ai-sandbox-daytona
@tanstack/ai-sandbox-docker
@tanstack/ai-sandbox-local-process
@tanstack/ai-sandbox-sprites
@tanstack/ai-sandbox-vercel
@tanstack/ai-solid
@tanstack/ai-solid-ui
@tanstack/ai-svelte
@tanstack/ai-utils
@tanstack/ai-vue
@tanstack/ai-vue-ui
@tanstack/openai-base
@tanstack/preact-ai-devtools
@tanstack/react-ai-devtools
@tanstack/solid-ai-devtools
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Changes
While using remote MCP servers via
@tanstack/ai-mcp, I found that toolannotations are stripped at discovery. Since they indicate how risky a tool call
is (
readOnlyHint,destructiveHint), dropping them loses information a hostneeds to label tools and gate approvals.
Discovery previously stamped only
serverToolName/serverId/uiResourceUriontometadata.mcp. This PR also forwards:annotations— the server's object verbatim, omitted when absent so theexplicit
tools([...defs])path can't blank out caller-supplied metadata.title— display name resolved with the spec's precedence(
title→annotations.title→name).Both the auto-discovery and explicit paths now go through one shared
toolMcpMetadata()so they can't drift (the explicit path was a second, thinnerdrop site). Also exports
McpToolMetadata—Tool.metadataisRecord<string, any>, so an exported shape is what lets consumers read theblock without a cast — and re-exports the SDK's
ToolAnnotations.Display-only and non-breaking: the model-facing tool
name,description, andprovider payload are unchanged; a
prefixstill applies to the name, not thetitle. Annotations are treated as spec hints — docs show gating that defaults to
requiring approval and relaxes only on
readOnlyHint, never as a securityboundary.
Test plan
pnpm test:pr— green (includes kiira over the new docs snippets).pnpm --filter @tanstack/ai-e2e test:e2e -- --grep "mcp"— 8/8 pass. Thefixture-driven chat specs passing is the check that the provider payload
didn't change.
undefined)when the server declares none; title precedence across all three tiers;
prefix-vs-title independence. Both paths also covered against a real
in-memory server declaring a title and all four hints.
get_guitar_pricedeclares a title + hints;api.mcp-status-testreturns the forwarded metadata andmcp-status.spec.tsasserts it. (Coverage lives in the MCP specs rather than
tools-test-scenarios.tssince this is MCP discovery metadata, not coretool-system behavior.)
✅ Checklist
pnpm run test:pr.🚀 Release Impact
(minor,
@tanstack/ai-mcp).Summary by CodeRabbit
New Features
Documentation