We are pleased to announce the release of MCP Servers 1.1.0, bringing new configuration options for HTTP-based deployments and expanded command-line capabilities for managing database connections.
The new version makes it easier to control how MCP Servers are exposed over HTTP, host multiple MCP Servers under a single hostname, and configure connections directly from the command line.
More control over HTTP endpoints
MCP Servers running over the HTTP transport protocol now support the new HttpAddress configuration property. It allows you to specify the address the server binds to, providing greater control over how the MCP Server is exposed in different deployment environments.
Host multiple MCP Servers under one hostname
Version 1.1.0 also introduces the HttpRoutePrefix configuration property. With this option, you can publish multiple MCP Servers under the same hostname and assign a separate URL path to each server.
For example, different MCP Servers can be exposed through endpoints such as:
https://example.com/mysqlhttps://example.com/postgresqlhttps://example.com/oracle
This makes it easier to organize and deploy multiple MCP Servers behind a single host or reverse proxy.
Manage connections entirely from the command line
The config command has been extended with new subcommands for connection management. You can now configure and manage MCP Server connections entirely from the command line, without manually editing configuration files.
This improvement makes configuration more convenient and is especially useful for automated deployments, scripts, and CI/CD workflows.
Get MCP Servers 1.1.0
MCP Servers 1.1.0 provides more flexibility for HTTP deployments and simplifies connection configuration and automation. Upgrade to the latest version to take advantage of the new HTTP settings and command-line connection management capabilities.
