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
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago