MCPify

Overview

MCPify bridges existing ASP.NET Core APIs and external OpenAPI specifications with the Model Context Protocol. It dynamically exposes API operations as MCP tools while supporting hybrid local and external APIs. The library offers robust OAuth 2.0 authentication with PKCE, JWT validation, and scope enforcement, fully compliant with the MCP Authorization Specification. With both Stdio and Http transport options, it's designed for production environments with proper logging and error handling.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

• login_auth_code_pkce

  Handles OAuth 2.0 authorization code flow with PKCE for authentication

  Try:Please login to the serviceTry:Start authentication flowTry:Connect to the API with my credentials

Note: The README indicates that MCPify dynamically converts OpenAPI operations to MCP tools, but doesn't list specific tool names. Only the 'login_auth_code_pkce' tool is explicitly named in the authentication section. Other tools would be genera

Comparable tools

Installation

dotnet add package MCPify

builder.Services.AddMcpify(options => {
    options.Transport = McpTransportType.Stdio;
    options.LocalEndpoints = new LocalEndpointsOptions {
        Enabled = true,
        ToolPrefix = "myapp_"
    };
});

{
  "mcpServers": {
    "my-app": {
      "command": "dotnet",
      "args": [
        "run",
        "--project",
        "/absolute/path/to/YourProject.csproj",
        "--",
        "--Mcpify:Transport=Stdio"
      ]
    }
  }
}

FAQ

What authentication methods does MCPify support?

MCPify provides comprehensive OAuth 2.0 support with Authorization Code Flow, PKCE, JWT validation, scope enforcement, and automatic token refresh.

Can MCPify work with external OpenAPI specs?

Yes, it supports exposing external APIs from URLs or local files while also supporting local ASP.NET Core endpoints simultaneously.

Compare MCPify with