MCP.so
Sign In

AISDK MCP Bridge

@vrknetha

About AISDK MCP Bridge

Bridge package enabling seamless integration between Model Context Protocol (MCP) servers and AI SDK tools. Supports multiple server types, real-time communication, and TypeScript.

Basic information

Category

Developer Tools

Transports

stdio

Publisher

vrknetha

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is AISDK MCP Bridge?

A bridge package that enables seamless integration between the Model Context Protocol (MCP) and the AI SDK, allowing efficient communication and tool execution from MCP servers within AI‑powered applications. It is designed for developers who use the AI SDK and want to connect it with MCP‑compatible servers.

How to use AISDK MCP Bridge?

Install via npm install aisdk-mcp-bridge. Create an mcp.config.json file in your project root to define MCP servers, then import and call initializeMcp(), getMcpTools(), and cleanupMcp() from the package. Use the returned tool set with AI SDK functions like generateText.

Key features of AISDK MCP Bridge

  • Support for Node.js, Python, and UVX MCP servers
  • Multi‑server support with independent configuration
  • Flexible configuration through mcp.config.json
  • Full TypeScript type definitions
  • Robust error handling and logging
  • Choice of stdio or SSE communication modes

Use cases of AISDK MCP Bridge

  • Integrate a Twitter MCP server with an AI application
  • Combine a Firecrawl web scraping MCP server with an AI model
  • Use SSE‑based MCP servers for real‑time streaming tasks
  • Manage multiple MCP servers from a single codebase

FAQ from AISDK MCP Bridge

What runtimes are required?

Node.js 20.x or higher and npm 7.x or higher.

How do I configure MCP servers?

Create an mcp.config.json file in your project root listing each server’s command, arguments, environment variables, and optional mode (stdio or SSE).

Which communication modes does the bridge support?

It supports stdio mode (default, direct I/O) and SSE mode (Server‑Sent Events for real‑time streaming with built‑in reconnection).

How can I get tools from a single server instead of all servers?

Pass the serverName option to getMcpTools({ serverName: 'your-server' }).

How do I enable debug logging?

Set the DEBUG environment variable, for example DEBUG=mcp:* npm start, to see detailed logs on initialization, tool registration, and performance metrics.

Comments

More Developer Tools MCP servers