furi

CLI & API for MCP management

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio ashwwwin-furi node path/to/server.js \
  --env GITHUB_KEY="your-github-token (optional, to increase GitHub API rate limits)" \
  --env HTTP_AUTH_TOKEN="your-secret-token (optional, enables sudo/protected routes)"

How to use

furi is a CLI and HTTP API server that manages multiple MCPs (Minecraft-compatible packages) from public GitHub repositories. It can add MCPs by repository, start and stop them, expose a unified HTTP API for all running MCPs, and aggregate each MCP's available tools. The CLI lets you install, rename, remove, and configure MCPs, and you can launch tools within each MCP or inspect their status and logs. The HTTP API exposes public endpoints for listing MCPs and tools, calling tools, and, when enabled with sudo routes, performing administrative operations on packages and MCP instances. In addition, Furikake’s aggregator server can publish all tools via SSE for clients or provide a stdio-based transport for clients that rely on stdin/stdout. The distribution is Bun/TypeScript-based, with a strong emphasis on pluggability and a consistent JSON-oriented protocol for tool calls and responses.

How to install

Prerequisites:

A Unix-like OS (macOS/Linux) or Windows with a compatible shell
Node.js installed (or Bun installed if you prefer Bun-based workflows)
curl (for installation script)

Installation steps:

Install Furikake (Furi): curl -fsSL https://furi.so/install | bash
Verify installation: furi
Optional: upgrade to the latest version when needed: furi upgrade
Prepare environment variables (example):
- Create a .env file or export values in your shell export HTTP_AUTH_TOKEN=your-secret-token export GITHUB_KEY=your-github-token
Start the MCP management server (example using a local server.js entry):
- Ensure you have a Node.js environment and your server entry is accessible node path/to/server.js
If you are packaging this MCP server for deployment, ensure the mcp_config is aligned with your runtime (see the JSON snippet in the mcp_config section).

Additional notes

Tips and notes:

The HTTP API supports public routes by default and sudo routes when HTTP_AUTH_TOKEN is configured. Secure your token to prevent unauthorized access.
GitHub API rate limits can be increased by providing GITHUB_KEY; this is especially helpful when installing many MCPs from public repos.
All MCPs and their configuration/logs are stored under the .furikake directory; use furi where to locate this directory for backup or inspection.
The aggregator supports SSE and stdio transports. Use furi meta start for SSE, or furi connect for stdio-based clients.
When using the CLI -e flag to pass environment variables to started MCPs, ensure the JSON is valid; it will be stored and reused for subsequent starts.
If you encounter issues starting an MCP, check the MCP's logs in the .furikake directory and verify that the server entry point (path/to/server.js) is correct for your setup.