MCP.so
Sign In

MCP Auto Tool Switcher

@Maiks-Dev-Team

About 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.

Basic information

Category

Other

Runtime

node

Transports

stdio

Publisher

Maiks-Dev-Team

Config

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

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

FAQ from MCP Auto Tool Switcher

What is the current status of the project?

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

What are the runtime dependencies?

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

Where is server configuration stored?

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

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.

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.

Comments

More Other MCP servers