FluidMCP CLI

What is FluidMCP CLI?

FluidMCP CLI is a command-line tool for managing and running MCP (Model Context Protocol) servers. It allows you to install, configure, and run MCP packages from the FluidMCP registry, with features like interactive environment variable configuration, automatic port management, secure mode with bearer token authentication, and S3-based configuration management.

How to use FluidMCP CLI?

Install via pip: pip install fluidmcp. Use commands like fluidmcp install <author/package@version>, fluidmcp list, fluidmcp run <package|all|file>, and fluidmcp edit-env <authorname/package@version>. Options include --master for S3-based centralized config, --secure with bearer token, --port, --start-server, --file, --s3, and --force-reload.

Key features of FluidMCP CLI

• Install MCP packages from the FluidMCP registry
• Interactive environment variable configuration
• Run individual or multiple MCP servers
• Secure mode with bearer token authentication
• S3-based configuration management
• Automatic port management and conflict resolution

Use cases of FluidMCP CLI

• Install and run specific MCP server versions for AI tooling
• Centralize server configuration via S3 for multi-environment deployments
• Run all installed packages simultaneously with automatic port assignment
• Securely deploy production MCP servers with bearer token authentication
• Manage environment variables interactively for installed packages

FAQ from FluidMCP CLI

How does FluidMCP CLI differ from manually running MCP servers?

FluidMCP CLI automates installation, configuration, and running of MCP servers from a central registry, handles environment variables, port conflicts, and supports secure mode with authentication, unlike manual setup.

What are the runtime requirements?

FluidMCP CLI requires Python (installed via pip) and access to the FluidMCP registry. For master mode, S3 credentials must be configured via environment variables (S3_BUCKET_NAME, S3_ACCESS_KEY, S3_SECRET_KEY, S3_REGION).

Where does data live?

Installed packages are stored locally in a .fmcp-packages directory. In master mode, server metadata and environment files are stored in an S3 bucket. Package downloads use S3 pre-signed URLs from the registry.

What transport or authentication does it support?

It uses HTTP/HTTPS to communicate with the FluidMCP registry for package downloads. Secure mode adds bearer token authentication for inter-server communication via a SuperGateway.

Can I use local configuration files instead of the registry?

Yes. The run command supports --file to run from a local JSON configuration file, and --s3 to run from an S3 presigned URL configuration file.