MCP.so
ログイン

MCP Auto Tool Switcher

@Maiks-Dev-Team

基本情報

カテゴリ

その他

トランスポート

stdio

作者

Maiks-Dev-Team

MCP Auto Tool Switcher について

A MCP server that allows your client to switch MCP servers so you don't run in to a tool limit.

#mcp#auto-tool-switcher#server-management

MCP Auto Tool Switcher の設定

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

{
  "mcpServers": {
    "auto-tool-switcher": {
      "command": "node",
      "args": [
        "cascade-mcp-server.js"
      ]
    }
  }
}

MCP Auto Tool Switcher のツール

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

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

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is MCP Auto Tool Switcher?

MCP Auto Tool Switcher is a system for managing MCP servers, tools, prompts, and resources. It acts as a modular MCP server that forwards tools from other MCP servers.

How to use MCP Auto Tool Switcher?

Install dependencies with npm install, then start the server with node cascade-mcp-server.js. Use the provided tools such as mcp0_servers_list, mcp0_servers_enable, mcp0_servers_disable, and mcp0_refresh_tools to manage servers and discover tools.

Key features of MCP Auto Tool Switcher

  • Cross-platform support (Windows, macOS, Linux)
  • Add, remove, enable, and disable MCP servers
  • List, invoke, and preview tools, prompts, and resources
  • Passthrough forwarding for tools from other MCP servers
  • Automatic startup of all enabled servers on initialization
  • Intelligent caching for improved performance

Use cases of MCP Auto Tool Switcher

  • Centralized management of multiple MCP servers
  • Quick enable/disable of servers during development
  • Automatic startup of required servers on project launch
  • Discovery and invocation of tools across different servers

よくある質問

1

What is the current status of the project?

The project is in early development. Features are experimental, incomplete, and subject to rapid change.

2

What are the runtime dependencies?

Node.js is required. Install project dependencies with `npm install`.

3

Where is server configuration stored?

All server configuration is stored in `servers.json` and `mcp-config.json` in the project root.

4

What future improvements are planned?

An Electron tray client is planned for system-level management with a visual interface for adding, editing, and removing servers.

5

Does the server support authentication or custom transports?

The README does not mention authentication or transport configuration. It is a basic MCP server acting as a passthrough.

コメント

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