QuickMCP

QuickMCP is a .NET toolkit that helps you rapidly generate and serve MCP (Model Context Protocol) servers from OpenAPI, Swagger, or Google Discovery specifications. It also offers tools to build Claude Desktop extensions (.mcpb) with AI-generated metadata, and provides a configurable library with a CLI for quick deployment. You can serve a server directly from a spec URL, or build a reusable configuration file that defines endpoints, authentication methods, and transport options. The toolkit supports multiple authentication schemes (API Key, Basic, Bearer, OAuth 2.0, and custom headers) and allows you to extend authentication via a custom interface, making it easy to integrate with your existing security policy. With QuickMCP you can generate tooling around path filtering, HTTP customization, error handling, and logging, and then run or distribute these servers alongside MCP clients like Claude Desktop. Use the CLI to generate server configurations, create Claude Desktop extensions, or run a server directly from a spec, and manage stored server configurations for quick access.

Prerequisites:

• Install the .NET SDK (recommended latest LTS): https://dotnet.microsoft.com/download
• Ensure dotnet is available on your PATH

Installation steps:

1. Install the QuickMCP CLI globally as a .NET tool dotnet tool install -g QuickMCP.CLI

2. Verify installation dotnet tool list -g quickmcp --help

3. (Optional) Install the QuickMCP library into your project dotnet add package QuickMCP

4. (Optional) Initialize a sample configuration or build a CLI-generated config quickmcp build config --spec-url https://petstore.swagger.io/v2/swagger.json --output-path ./config

Notes:

• The CLI commands follow the QuickMCP syntax shown in the README: serve, build, add, list, delete, etc.
• You can run servers directly from a specification URL or from a prepared configuration file.

Tips and caveats:

• Authentication customization is supported; you can add ApiKey, Basic, Bearer, OAuth2, or custom header authentication in your generated configuration.
• When using Claude Desktop extensions, you can generate .mcpb files with AI-generated metadata to enhance your MCP endpoints.
• If you plan to distribute your server configurations, consider storing them in a central repository and using the CLI’s add/list features to manage named servers for quick access.
• Ensure your OpenAPI/Swagger/Google Discovery spec is accessible from the environment running the MCP server (network access, CORS considerations not needed for server-side specs).
• If you run into issues, check that the CLI and .NET runtime versions are compatible with your project, and verify that any required environment variables (like config paths or API keys) are correctly set.