MCP.so
Sign In

MCP Connector

@JohanKoppenaal

Basic information

Category

Other

Transports

stdio

Author

JohanKoppenaal

About MCP Connector

No overview available yet

MCP Connector config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "n8n-mcp-server-johankoppenaal": {
      "command": "npx",
      "args": [
        "@typingmind/mcp",
        "<auth-token>"
      ]
    }
  }
}

MCP Connector tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is MCP Connector?

MCP Connector is a lightweight server that can run and manage multiple Model Context Protocol (MCP) servers, specifically designed to integrate with TypingMind. It provides an easy way to run MCP servers on your local computer or a remote server, making it possible to connect your custom AI models or tools with TypingMind through a simple REST API.

How to use MCP Connector?

Run the server using npx @typingmind/mcp <auth-token> (no install required). Replace <auth-token> with your authentication token provided by TypingMind. For HTTPS, set the CERTFILE and KEYFILE environment variables. To connect to TypingMind, paste your server address and token on the TypingMind MCP integration page.

Key features of MCP Connector

  • Runs and manages multiple MCP servers simultaneously
  • Integrates with TypingMind via REST API
  • Supports local and remote server deployment
  • Provides health check, start, restart, list, and delete endpoints
  • Authentication via Bearer token
  • Optional HTTPS support with SSL certificates

Use cases of MCP Connector

  • Connect custom AI models or tools hosted on your local machine to TypingMind
  • Deploy on a remote server to share MCP capabilities with TypingMind users
  • Run multiple MCP clients side‑by‑side for different tool sets
  • Use within a development workflow to test MCP tools before production

Frequently asked questions

1

What is MCP Connector and how does it differ from a standard MCP server?

MCP Connector is a manager that can run multiple MCP servers and exposes them through a REST API for TypingMind integration, whereas a standard MCP server typically runs a single tool set.

2

What are the runtime requirements for MCP Connector?

Node.js version 14 or later is required. The server can be run using `npx` without global installation.

3

Where does MCP Connector store data or configuration?

The README does not specify any persistent storage; configuration is provided via environment variables and the command‑line authentication token.

4

What ports does MCP Connector use and how can I change them?

By default, the server chooses port `50880` or `50881`. You can specify a different port using the `PORT` environment variable.

5

What authentication and transport does MCP Connector support?

All API endpoints require an `Authorization: Bearer <auth-token>` header. The server runs over HTTP by default, but HTTPS can be enabled by setting `CERTFILE` and `KEYFILE` environment variables.

Comments

More Other MCP servers