Langchain MCP Tools Ts

🚀 MCP Toolbox

The MCP (Model Configuration Protocol) Toolbox is designed to simplify workflows related to the Model Configuration Protocol. It enables users to easily start and manage MCP servers via configuration files or command - line parameters and interact with these servers through a consistent interface.

🚀 Quick Start

Configure the Local MCP Server

You can start a local MCP service via a configuration file or command - line parameters. For example:

const config = {
    "local-server": {
        command: 'node my-mcp-server.js',
        args: ['--port', '3000']
    }
};

// Start the server
mcpToolbox.start(config);

Connect to a Remote MCP Service

To connect to a remote MCP service, simply specify the URL in the configuration file:

const config = {
    "remote-server": {
        url: 'http://example.com/mcp'
    }
};

// Connect to the remote server
mcpToolbox.connect(config);

✨ Features

• Simplify the workflow related to the Model Configuration Protocol.
• Provide a consistent interface to interact with MCP servers.
• Support starting and managing local and remote MCP servers.

📦 Installation

You can install the MCP Toolbox via npm or yarn:

npm install mcp-toolbox
# Or
yarn add mcp-toolbox

After installation, you can import and use it in any JavaScript file:

const mcpToolbox = require('mcp-toolbox');
// Or
import { default as mcpToolbox } from 'mcp-toolbox';

💻 Usage Examples

Basic Usage

Start a local server and capture logs:

const mcpToolbox = require('mcp-toolbox');
const fs = require('fs');

// Create a log file descriptor
const logFd = fs.openSync('mcp-server.log', 'w');

const config = {
    "local-mcp": {
        command: './server.js',
        args: ['--mode', 'production'],
        cwd: '/path/to/working/dir',
        stderr: logFd
    }
};

// Start the server
mcpToolBox.start(config);

Advanced Usage

Connect to a remote service that requires OAuth authentication:

const mcpToolbox = require('mcp-toolbox');
const { MyOAuthProvider } = require('./auth');

const config = {
    "remote-mcp": {
        url: 'https://example.com/mcp',
        sseOptions: {
            authProvider: new MyOAuthProvider()
        }
    }
};

// Connect to the remote server
mcpToolbox.connect(config);

📚 Documentation

Configuration Reference

Basic Configuration

• command: The command to start the local MCP service.
• args: An array of parameters passed to the command.
• url: The URL of the remote MCP service.

Advanced Configuration

• cwd: The working directory when executing the command.
• stderr: The file descriptor to capture error output.
• authProvider: Provide a custom authentication provider for services that require authentication.

Experimental Features

Remote MCP Service Support

For remote MCP services provided via SSE (Server - Sent Events) or WebSocket, configure as follows:

const config = {
    "sse-server": {
        url: `http://${sse_server_host}:${sse_server_port}`
    },
    "websocket-server": {
        url: `ws://${websocket_server_host}:${websocket_server_port}`
    }
};

Authentication Support

If your MCP service requires authentication, you can implement it through a custom authentication provider:

class MyOAuthProvider {
    authenticate() {
        // Implement your authentication logic
    }
}

const config = {
    "remote-server": {
        url: 'http://protected.example.com/mcp',
        sseOptions: {
            authProvider: new MyOAuthProvider()
        }
    }
};

Error Output Redirection

By specifying the stderr property, you can redirect error output to a custom file or stream:

const fs = require('fs');
const config = {
    "local-server": {
        command: 'node my-server.js',
        stderr: fs.openSync('error.log', 'w')
    }
};

Limitations

• Currently, only local MCP services started via Node.js are supported.
• For remote services, only SSE and WebSocket protocols are supported at present.

Change Log

v1.0.0 (2023 - 10 - 01)

• Initial version released, including basic functions and documentation.

v1.1.0 (2023 - 11 - 01)

• Added support for WebSocket.
• Optimized the error handling mechanism.

For more detailed information, please refer to MCP Toolbox Documentation.