ai sdk tools
tool judged 7% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2025-W37 | 1 | 1 |
| 2026-W05 | 1 | 1 |
| 2026-W20 | 1 | 1 |
| 2026-W24 | 1 | 1 |
| 2026-W34 | 2 | 1 |
| 2026-W36 | 1 | 1 |
In their words
Tools mode exposes memory as two Zod-validated AI SDK tools the model calls itself — ordinary tool calls, so they appear in your UI stream where users (and you, at 2am) can watch the agent remember: const nams = createNams({ apiKey: process.env.MEMORY_API_KEY!
It now powers code mode in the AI SDK where existing AI SDK tools are mapped to host functions, while the Run SDK handles their sandboxed execution.
Around that call, adapters handle the wiring: @vercel/connect/eve supplies the credentials behind an agent's connections @vercel/connect/chat hooks Connect into Chat SDK adapters @vercel/connect/betterauth and @vercel/connect/authjs produce provider configs for Better Auth and Auth.js @vercel/connect/ai-sdk and @vercel/connect/mcp do the same for AI SDK tools and MCP clients, whether your agent ca
Better Auth ( @vercel/connect/betterauth ) and Auth.js ( @vercel/connect/authjs ) get provider configs in the shape they expect, and @vercel/connect/ai-sdk and @vercel/connect/mcp do the same for AI SDK tools and MCP clients.
Chat SDK now includes AI SDK tools
Get started with Parallel for your AI applications through AI Gateway, the AI SDK tool package, or Vercel Marketplace.
It is a CLI that generates static AI SDK tool definitions from any MCP server.