Swiss Army Knife For MCP Servers MCP Server

A command-line interface for interacting with MCP (Model Context Protocol) servers using both stdio and HTTP transport.

Local serverstdioTypeScript

What is the Swiss Army Knife For MCP Servers MCP server?

A command-line interface for interacting with MCP (Model Context Protocol) servers using both stdio and HTTP transport. The swiss army knife for mcp servers mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

MCP Tools provides a versatile CLI for working with Model Context Protocol (MCP) servers. It enables you to:

Adding it to your client

The server ships on npm as @modelcontextprotocol/server-filesystem, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • Windsurf — Cursor
  • Commands — MCP Tools includes several core commands for interacting with MCP servers:
  • Bonus — Add official GitHub MCP Server to Windsurf, Cursor and VS Code at once:

Configuration

You will need one environment variable: GITHUB_PERSONAL_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the swiss army knife for mcp servers mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Swiss Army Knife For MCP Servers's toolset — Windsurf, Commands, Bonus — is a fair guide to whether it matches your workflow. It is maintained by f; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Swiss Army Knife For MCP Servers's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
WindsurfCursor
CommandsMCP Tools includes several core commands for interacting with MCP servers:
BonusAdd official GitHub MCP Server to Windsurf, Cursor and VS Code at once:

How to install the Swiss Army Knife For MCP Servers MCP server

{
  "mcpServers": {
    "mcptools": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_PERSONAL_ACCESS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Swiss Army Knife For MCP Servers to Windsurf.
  • Use Swiss Army Knife For MCP Servers to Commands.
  • Use Swiss Army Knife For MCP Servers to Bonus.

Frequently asked questions

On macOS, use Homebrew: `brew tap f/mcptools && brew install mcp`. On Windows and Linux, install from source: `go install github.com/f/mcptools/cmd/mcptools@latest`. The binary is installed as `mcp` (or `mcpt` / `mcptools` to avoid conflicts).