vrknetha/aisdk-mcp-bridge

A bridge package that enables seamless integration between the Model Context Protocol (MCP) and AI SDK, allowing for efficient communication and tool execution between MCP servers and AI models.
## Features
Seamless integration between MCP servers and AI SDK
Support for various MCP server types (Node.js, Python, UVX)
Multi-server support with independent configuration
Flexible configuration through mcp.config.json
TypeScript support with full type definitions
Robust error handling and logging
Easy-to-use API for tool execution
## Installation
bash
npm install aisdk-mcp-bridge
## Quick Start
1. Create an mcp.config.json file in your project root:
json
"mcpServers": {
"twitter-mcp": {
"command": "npx",
"args": ["-y", "@enescinar/twitter-mcp"],
"env": {
"APIKEY": "your-twitter-api-key",
"APISECRETKEY": "your-twitter-api-secret",
"ACCESSTOKEN": "your-twitter-access-token",
"ACCESSTOKENSECRET": "your-twitter-access-token-secret"
},
"firecrawl": {
"command": "npx",
"args": ["-y", "mcp-server-firecrawl"],
"env": {
"FIRECRAWLAPIKEY": "your-firecrawl-api-key",
"FIRECRAWLAPIURL": "https://api.firecrawl.com"
2. Import and use the bridge in your code:
typescript
import { generateText } from 'ai';
import { google } from '@ai-sdk/google';
import { getMcpTools, cleanupMcp, initializeMcp } from 'aisdk-mcp-bridge';
import dotenv from 'dotenv';
dotenv.config();
async function main() {
try {
// Initialize MCP
await initializeMcp({ debug: true });
// Get tools from all servers
const allTools = await getMcpTools({ debug: true });
// Or get tools from a specific server
const twitterTools = await getMcpTools({
debug: true,
serverName: 'twitter-mcp',
});
// Use tools with AI SDK
const result = await generateText({
model: google('gemini-1.5-pro'),
messages: [
role: 'system',
content:
'You are an AI assistant that uses various tools to help users.',
},
role: 'user',
content: 'Your task description here',
},
],
tools: twitterTools, // or allTools for all available tools
});
console.log('Result:', result.text);
} finally {
// Clean up resources
await cleanupMcp();
main().catch(error => {
console.error('Error:', error);
process.exit(1);
});
## Configuration
The mcp.config.json file supports multiple servers and communication modes. Each server can be configured independently.
### Server Configuration Examples:
### Twitter MCP Server
json
"mcpServers": {
"twitter-mcp": {
"command": "npx",
"args": ["-y", "@enescinar/twitter-mcp"],
"env": {
"APIKEY": "your-twitter-api-key",
"APISECRETKEY": "your-twitter-api-secret",
"ACCESSTOKEN": "your-twitter-access-token",
"ACCESSTOKENSECRET": "your-twitter-access-token-secret"
### Firecrawl Server
json
"mcpServers": {
"firecrawl": {
"command": "npx",
"args": ["-y", "mcp-server-firecrawl"],
"env": {
"FIRECRAWLAPIKEY": "your-firecrawl-api-key",
"FIRECRAWLAPIURL": "https://api.firecrawl.com"
### SSE Server
json
"mcpServers": {
"sse-server": {
"command": "node",
"args": ["./server.js"],
"mode": "sse",
"sseOptions": {
"endpoint": "http://localhost:3000/events",
"headers": {},
"reconnectTimeout": 5000
## Server Modes
The bridge supports different communication modes:
1. stdio Mode (Default)
Direct communication through standard input/output
Best for simple integrations and local development