How to Use the Metatext MCP in Vercel AI SDK

Q: Does Metatext expose dataset records to Vercel AI SDK?

It does. You can pull existing records using listdatasetrecords and inject them directly into your prompt context.

Stream Metatext model results directly into your Vercel AI SDK frontends for real-time NLP interactions.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Metatext MCP to Vercel AI SDK

Create your Vinkius account to connect Metatext 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

Setup Metatext with Vercel AI SDK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Live NLP Inference

Trigger `run_model_inference` directly from your edge functions to pipe results to the user interface. Your frontend renders the output as the tokens arrive. Stop waiting for spinners. The AI client handles the stream, so your users see data populate the moment the model generates it.

Dataset Management

Call `create_dataset_record` to push user inputs into your storage without leaving the application context. It keeps your data flow tight and synchronous. Your application state stays in sync with your backend records. You manage your content updates through standard tool calls.

Model Discovery

Query `list_nlp_models` to populate dropdowns or filters in your UI. You can show users exactly which models are ready for their specific task. Use `search_nlp_models` to find specific architectures on the fly. It makes your application dynamic and responsive to user input.

Setup guide

Set up Metatext 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

Install dependencies

Run npm install ai @modelcontextprotocol/sdk plus your preferred model provider (e.g. @ai-sdk/openai).
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

Discover and use tools

Call mcpClient.tools() to auto-discover all Metatext tools. Pass them directly to generateText() or streamText() — no manual schema definitions needed.
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 Metatext transactions",
});

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Metatext. 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.

Connect Metatext now

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 Metatext MCP in Vercel AI SDK

You pipe the output of your tool call into a transformation function before it hits your state. This lets you strip unnecessary metadata before rendering.

Yes. Since the MCP server communicates over HTTP, it plays nice with edge runtimes. Keep your payload sizes small for the best latency.

It does. You can pull existing records using `list_dataset_records` and inject them directly into your prompt context.

The MCP client will throw an error that you can catch in your standard promise chain. Handle it like any other API failure in your frontend code.

Use environment variables on your server side to store your token. Never expose the raw key in your client-side bundle.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.