home / mcp / mcp connect mcp server

MCP Connect MCP Server

Exposes local MCP servers via HTTP bridges and Streamable HTTP for easy external access and orchestration.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "evalsone-mcp-connect": {
      "command": "uvx",
      "args": [
        "mcp-server-fetch"
      ],
      "env": {
        "E2B_API_KEY": "your-e2b-api-key",
        "ACCESS_TOKEN": "<optional_token>",
        "ALLOWED_ORIGINS": "https://yourdomain.com,https://app.yourdomain.com",
        "NGROK_AUTH_TOKEN": "your-token-here",
        "E2B_MCP_AUTH_TOKEN": "your-secure-token"
      }
    }
  }
}

MCP Connect acts as a lightweight gateway that makes local MCP servers accessible over HTTP, enabling remote tools to interact with your MCP-backed services securely and efficiently.

How to use

You can access local MCP servers from external clients by exposing them through an HTTP bridge or via a Streamable HTTP route. Each MCP server runs locally and speaks stdio, while the gateway translates calls into HTTP endpoints your clients can call. You get dual modes: use a Streamable HTTP route for ongoing conversations or a classic HTTP bridge for request/response patterns. You can also enable a public tunnel to expose endpoints publicly and manage access with bearer tokens.

How to install

Prerequisites you need before starting are Node.js version 22.0.0 or newer and a package manager such as npm or yarn.

# 1) Clone the project
git clone https://github.com/EvalsOne/MCP-connect.git

# 2) Change into the project directory
cd mcp-connect

# 3) Install dependencies
npm install

Additional configuration and usage notes

Configure a local MCP server by adding a stdio-based entry to the MCP server configuration. The configuration demonstrates how to expose a local MCP server over an HTTP bridge.

{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"],
      "description": "HTTP/HTTPS content fetcher"
    }
  }
}

Security and access

If you enable access control, MCP Connect supports bearer token authentication. Include the Authorization header as Bearer <token> in requests when an access token is configured.

You can restrict cross-origin requests by setting ALLOWED_ORIGINS in the environment when running in production.

Public exposure with Ngrok

To expose endpoints publicly, install and configure Ngrok with an auth token, then start the tunnel to generate public URLs that forward to your MCP bridge.

Available tools

tools/list

List available tools you can call against an MCP server via the HTTP bridge or Streamable HTTP route.

tools/call

Invoke a specific tool on a server with provided arguments and capture the result.

prompts/list

List available prompts that can guide interactions with MCP-connected servers.

prompts/get

Retrieve a specific prompt by name or identifier.

resources/list

List resources the MCP server can access or generate.

resources/read

Read a specified resource from the MCP server.

resources/subscribe

Subscribe to live updates for a resource.

resources/unsubscribe

Unsubscribe from a live resource feed.

completion/complete

Request a text completion for a given prompt or context.

logging/setLevel

Adjust the logging verbosity at runtime.