MCP.so
ログイン

MCP Connector

@TypingMind

基本情報

カテゴリ

その他

トランスポート

stdio

作者

TypingMind

MCP Connector について

Run MCP servers securely.

MCP Connector の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

MCP Connector のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is MCP Connector?

MCP Connector is a lightweight server that runs and manages multiple Model Context Protocol (MCP) servers, designed to integrate with TypingMind. It enables running MCP servers on a local computer or remote server and connecting custom AI models or tools to TypingMind via a simple REST API.

How to use MCP Connector?

Run instantly with npx @typingmind/mcp@latest <auth-token> (no install required) or provide the token via the MCP_AUTH_TOKEN environment variable. Keep the process running while using TypingMind. For Docker, build an image and run with mapped ports. Optionally set TIMEOUT, PORT, or HTTPS environment variables.

Key features of MCP Connector

  • Manages multiple MCP servers simultaneously
  • REST API with endpoints for clients and tools
  • Health check endpoint (/ping)
  • Tool call timeout configuration (default 60 seconds)
  • HTTPS support via certificate and key files
  • Docker support for containerized deployment

Use cases of MCP Connector

  • Connect custom AI models or tools to TypingMind
  • Run MCP servers locally or on a remote server
  • Proxy HTTP requests through the /mcp-connect endpoint
  • Manage and restart individual MCP clients via API

よくある質問

1

How do I get the authentication token?

The authentication token is provided by TypingMind. Follow the instructions at www.typingmind.com/mcp to obtain it.

2

What are the runtime requirements?

Node.js version 14 or later is required. Optionally, Docker can be used for containerized deployment.

3

Can MCP Connector run on a remote server?

Yes. Run it using `npx` or Docker on a remote server, optionally with a process manager like pm2 for persistence.

4

What is the default tool call timeout?

The default timeout is 60 seconds (60000ms). It can be customized via the `TIMEOUT` environment variable.

5

Which ports does the server use?

The server defaults to port 50880 or 50881. You can specify a different port using the `PORT` environment variable.

コメント

「その他」の他のコンテンツ