AISDK MCP Bridge

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

What is AISDK MCP Bridge?

AISDK MCP Bridge is a bridge package that facilitates seamless integration between Model Context Protocol (MCP) servers and AI SDK tools, enabling efficient communication and tool execution.

How to use AISDK MCP Bridge?

To use AISDK MCP Bridge, install it via npm and configure your mcp.config.json file to define the MCP servers you want to connect to. Then, import the bridge in your code and initialize it to start using the tools.

Key features of AISDK MCP Bridge?

  • Seamless integration between MCP servers and AI SDK
  • Support for various MCP server types (Node.js, Python, UVX)
  • Multi-server support with independent configuration
  • TypeScript support with full type definitions
  • Robust error handling and logging
  • Easy-to-use API for tool execution

Use cases of AISDK MCP Bridge?

  1. Integrating multiple AI tools from different MCP servers.
  2. Real-time communication between AI models and external services.
  3. Executing functions on MCP servers directly from your application.

FAQ from AISDK MCP Bridge?

  • What types of servers does AISDK MCP Bridge support?

It supports various server types including Node.js, Python, and UVX.

  • Is there TypeScript support?

Yes, AISDK MCP Bridge includes full TypeScript definitions.

  • How do I handle errors?

The bridge includes robust error handling and logging features.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vrknetha
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago