4,500+ servers built on MCP Fusion
Vinkius
DictionaryAPI.dev logo
Vinkius
Vercel AI SDK logo

How to Use the DictionaryAPI.dev MCP in Vercel AI SDK

Get instant English word definitions streamed directly into your React or Next.js frontend using the Vercel AI SDK.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

DictionaryAPI.dev MCP on Cursor AI Code Editor MCP Client DictionaryAPI.dev MCP on Claude Desktop App MCP Integration DictionaryAPI.dev MCP on OpenAI Agents SDK MCP Compatible DictionaryAPI.dev MCP on Visual Studio Code MCP Extension Client DictionaryAPI.dev MCP on GitHub Copilot AI Agent MCP Integration DictionaryAPI.dev MCP on Google Gemini AI MCP Integration DictionaryAPI.dev MCP on Lovable AI Development MCP Client DictionaryAPI.dev MCP on Mistral AI Agents MCP Compatible DictionaryAPI.dev MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Vercel AI SDK

Connect DictionaryAPI.dev MCP to Vercel AI SDK

Create your Vinkius account to connect DictionaryAPI.dev to Vercel AI SDK and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Stream definitions live to your Vercel AI SDK UI

Your users don't want to stare at a loading spinner while waiting for a dictionary lookup. This integration streams definitions in real-time as your agent pulls them from the API. By hooking the `get_word_definition` tool into your live stream, text pops up on the screen word by word, making the app feel incredibly fast. Setting this up takes seconds with the `@ai-sdk/mcp` package. Because the server runs inside Vinkius's V8 sandbox, you don't have to worry about managing API keys or dealing with cold starts. Just connect the endpoint and let your frontend render the data instantly.

Edge-ready linguistic lookups

Running dictionary checks at the edge shouldn't slow down your application. The `get_word_definition` tool works perfectly within Edge Functions, meaning you can run your linguistic agents closer to your users. It eliminates the latency penalty of traditional backend setups. This MCP Server handles the connection logic so your edge route stays lightweight. You get clean JSON payloads with phonetics and origins without bloated dependencies clogging your runtime environment.

Zero-setup authentication on Vinkius

Forget about managing multiple API tokens for your dictionary features. Vinkius handles the underlying authentication, giving you a single secure endpoint to call from your Vercel AI SDK setup. When your agent needs to check a word, it calls `get_word_definition` through our secure MCP Server gateway. The request is processed in an ephemeral sandbox that shuts down immediately after returning the definition, keeping your setup clean and secure.

Setup guide

Set up DictionaryAPI.dev MCP in Vercel AI SDK

Prerequisites

  • Node.js 18+ and a TypeScript project
  • ai + @modelcontextprotocol/sdk packages
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install dependencies

    Run npm install ai @modelcontextprotocol/sdk plus your preferred model provider (e.g. @ai-sdk/openai).

  2. 2

    Create the Streamable HTTP transport

    Use StreamableHTTPClientTransport with your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

  3. 3

    Discover and use tools

    Call mcpClient.tools() to auto-discover all DictionaryAPI.dev tools. Pass them directly to generateText() or streamText() — no manual schema definitions needed.

  4. 4

    Works with any model provider

    Swap openai("gpt-4o") for any AI SDK provider — Anthropic, Google, Mistral. The MCP tools work identically across all supported models.

index.ts
import { experimental_createMCPClient as createMCPClient } from "ai";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

const transport = new StreamableHTTPClientTransport(
  new URL("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
);

const mcpClient = await createMCPClient({ transport });
const tools = await mcpClient.tools();

const { text } = await generateText({
  model: openai("gpt-4o"),
  tools,
  prompt: "List recent DictionaryAPI.dev transactions",
});

console.log(text);
await mcpClient.close();

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DictionaryAPI.dev. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about DictionaryAPI.dev MCP in Vercel AI SDK

You should wrap your streamText call in a standard try-catch block. If the `get_word_definition` tool fails or times out, the Vercel AI SDK will catch the error, allowing you to display a clean fallback message in your UI instead of breaking the stream.
Yes, it works perfectly. The MCP client is fully compatible with edge environments because it relies on standard fetch requests. Just initialize the client in your route handler and pass the `get_word_definition` tool directly to your generator.
No, it only returns standard English dictionary definitions. The `get_word_definition` tool queries a public database, so it won't recognize internal company jargon or custom product names unless they are standard English words.
No. Vinkius manages the connection to the underlying dictionary service. You only need your single Vinkius token to access this MCP Server, saving you the hassle of managing third-party accounts.
Every text query sent to `get_word_definition` is processed in an isolated, ephemeral V8 sandbox. We do not store or log the specific English words you look up, and the sandbox is destroyed the moment the definition is sent back to your application.

Start using the DictionaryAPI.dev MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 1 tools

We've already built the connector for DictionaryAPI.dev. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 1 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.