Echo MCP

What BrunoKrugel/echo-mcp MCP server does

BrunoKrugel/echo-mcp MCP server connects an existing Echo web application to Model Context Protocol. It discovers or receives definitions for the application's routes and makes those operations available to MCP clients as tools. The API remains an Echo application; MCP support is added by creating the wrapper and mounting it at a route such as /mcp.

The project is intended for Go services built with the Echo framework. It does not describe a standalone gateway for arbitrary HTTP services. The routes must already exist in the Echo application that initializes the wrapper.

How it works

Create the MCP wrapper with the Echo instance, then mount it at an HTTP path. The example uses server.New(e), mounts /mcp, and starts the Echo server on port 8080. An MCP client can then connect to the resulting endpoint, such as http://localhost:8080/mcp.

BrunoKrugel/echo-mcp MCP server supports several ways to describe tool inputs and outputs. A raw OpenAPI YAML or JSON string can define the server metadata and operation schemas. Swaggo documentation can be enabled for applications that use Swagger annotations. Individual routes can receive manually registered schemas, while automatic inference provides a fallback for simpler endpoints.

Endpoint exposure can be narrowed by registering an inclusion list or excluding paths with wildcard patterns. This lets an application keep health checks or internal routes out of the MCP tool set.

Setup and configuration

Install the Go dependency with:

go get github.com/BrunoKrugel/echo-mcp

Import the package alongside Echo, initialize the wrapper with the existing *echo.Echo value, and mount the MCP route before starting the application. A base URL can be supplied through configuration when schema generation needs it. Swagger-based schemas are enabled with EnableSwaggerSchemas: true; raw definitions are supplied through OpenAPISchema.

The README shows an HTTP MCP client configuration with a URL and timeout. It does not document environment variables, authentication settings, or a separate executable command for launching the wrapper.

Tools and capabilities

• Expose Echo routes as MCP tools.
• Read operation definitions from raw OpenAPI YAML or JSON.
• Generate schemas from Swaggo annotations.
• Register request and query schemas for selected methods and paths.
• Infer basic path and body inputs when no richer schema is provided.
• Include or exclude endpoints from MCP exposure.

Limitations and notes

BrunoKrugel/echo-mcp MCP server is a library integrated into an Echo application, not a standalone MCP binary. The material does not specify built-in authentication, authorization, transport options beyond the mounted HTTP endpoint, or client-specific setup beyond a generic MCP HTTP configuration.

Manual schema registration is marked as work in progress in the project documentation. Automatic inference is described as suitable for basic path and body handling, so applications needing detailed validation or precise operation metadata should use OpenAPI, Swagger, or manual schema definitions instead. The project also does not state a license in the supplied material.