Skip to content

Releases: grparry/MCPInvoke

v2.1.0 - MCPBuckle 2.1.0 Integration & Workflow Improvements

19 Aug 16:03

Choose a tag to compare

πŸ”§ Enhanced Compatibility - MCPBuckle 2.1.0 Integration

This minor release ensures MCPInvoke applications are fully compatible with Claude Code CLI through integration with MCPBuckle 2.1.0's compatibility fixes.

Key Updates

  • MCPBuckle 2.1.0 Compatibility - Inherits Claude Code CLI compatibility fixes from MCPBuckle 2.1.0

    • Resolves optional route parameter parsing issues that affected Claude Code CLI integration
    • MCPBuckle dependency updated to support version 2.1.0+ with enhanced parameter name validation
    • All MCP tools generated through MCPInvoke now have property names compatible with Claude Code CLI requirements
  • Enhanced Parameter Binding - Continued compatibility with advanced parameter binding capabilities

    • Runtime parameter source detection remains fully functional with updated MCPBuckle dependency
    • Schema-aware parameter binding continues to mirror ASP.NET Core logic exactly
    • No breaking changes to existing MCPInvoke functionality

πŸš€ Improved Release Process

  • Professional Release Management - Updated GitHub workflow to use release-only triggers
    • Publish workflow now requires proper GitHub releases instead of simple tag pushes
    • Encourages comprehensive release documentation and manual review gates
    • Consistent with MCPBuckle's improved release process

βœ… Quality Assurance

  • All 137 Tests Passing - Full test coverage maintained with MCPBuckle 2.1.0 integration
  • Multi-Framework Support - Verified compatibility across .NET 6.0, 7.0, 8.0, and 9.0
  • Backward Compatibility - All existing MCPInvoke functionality preserved and enhanced

Impact

This minor release ensures that applications using MCPInvoke for MCP tool execution are fully compatible with Claude Code CLI. The dependency update to MCPBuckle 2.1.0 resolves parameter naming validation issues that could prevent Claude Code CLI from properly importing and executing MCP tools.

Full Changelog: v2.0.0...v2.1.0

MCPInvoke v1.3.1

17 Jul 18:47

Choose a tag to compare

What's New in v1.3.1

  • Aligned with MCPBuckle 1.5.1 - Updated to use the latest MCPBuckle version
  • Added Comprehensive Test Suite - First test suite with 53 tests covering all functionality

Changes

Added

  • Comprehensive Test Suite - Added 53 tests covering all functionality

Changed

  • Aligned with MCPBuckle 1.5.1 - Updated dependency to MCPBuckle 1.5.1

This release aligns MCPInvoke with the latest MCPBuckle version and adds the first comprehensive test suite to ensure reliability and quality.

MCPInvoke v1.3.0 - Full MCP Protocol Support

03 Jul 13:14

Choose a tag to compare

What's New in 1.3.0

MCPInvoke is now a complete Model Context Protocol (MCP) server implementation! This release transforms MCPInvoke from a tool execution endpoint into a full MCP server that's fully compatible with Claude Code CLI.

Added

  • Full MCP Protocol Support - Implements the complete MCP protocol specification:
    • initialize - Returns server capabilities with protocol version 2025-06-18
    • notifications/initialized - Acknowledges client initialization
    • tools/list - Returns the list of available tools with proper JSON Schema
    • tools/call - Executes tool methods (existing functionality)
  • Claude Code CLI Integration - Fully compatible with Anthropic's Claude Code CLI
  • JSON Schema Compliance - Fixed schema generation to comply with JSON Schema draft 2020-12
  • Improved Error Handling - Better error messages and protocol-compliant error responses

Fixed

  • Protocol version mismatch - Updated from 2025-05-06 to 2025-06-18
  • JSON Schema validation errors - Removed 'required' from property level, kept only at object level
  • Null description handling - Filtered out null descriptions from tool schemas

Claude Code CLI Integration

Your ASP.NET Core APIs can now be used directly with Claude Code CLI:

# Add your API as an MCP server
claude mcp add --transport http my-api http://localhost:5000/mcpinvoke

# Use your API tools in Claude
echo "Use the mcp__my-api__ToolName to perform task X" | claude

Breaking Changes

None - This release is fully backward compatible.

Installation

dotnet add package MCPInvoke --version 1.3.0

See the README for full documentation.

πŸš€ Initial Public Release of MCPInvoke! πŸš€

06 May 22:07

Choose a tag to compare

We are thrilled to announce the first official release of MCPInvoke, a lightweight .NET library designed to bridge the gap between AI agents and your ASP.NET Core applications using the Model Context Protocol (MCP).

MCPInvoke provides a robust execution endpoint for MCP tools discovered by its companion library, MCPBuckle. By leveraging the detailed tool definitions (including handler and method annotations from MCPBuckle v1.3.0+), MCPInvoke enables seamless invocation of your API actions as MCP tools.

Key Features in this Release:

MCP Tool Execution: Core functionality to execute MCP tools defined in your ASP.NET Core application.
Seamless Integration with MCPBuckle: Works directly with MCPBuckle (v1.3.0 or newer recommended) for dynamic tool discovery and definition. The McpBuckleToolDefinitionProvider translates MCPBuckle's discovered tools into executable definitions.
JSON-RPC Request Handling: Accepts JSON-RPC 2.0 compliant requests for invoking tools, making it compatible with a wide range of AI agent frameworks.
Flexible Service Architecture: Includes McpExecutionService for handling the core logic of tool invocation and parameter binding.
Multi-Framework Support: Targets .NET 6.0, .NET 7.0, .NET 8.0, and .NET 9.0.
Extensible: Designed to be easily integrated and extended within your existing ASP.NET Core projects.
Getting Started:

Add the MCPInvoke NuGet package to your ASP.NET Core project:
shell
CopyInsert in Terminal
dotnet add package MCPInvoke --version 1.0.0
Ensure you have MCPBuckle (v1.3.0 or higher) integrated for tool discovery.
Register MCPInvoke services in your Program.cs:
csharp
CopyInsert
// Example registration
builder.Services.AddMcpInvoke(options =>
{
// Configure McpInvoke options if needed
});
builder.Services.AddSingleton<IMcpToolDefinitionProvider, McpBuckleToolDefinitionProvider>(); // If using MCPBuckle
Expose the MCP invoke endpoint (typically via a controller action that uses McpExecutionService).
We believe MCPInvoke will significantly simplify the process of making your .NET applications accessible and controllable by AI agents. We look forward to your feedback and contributions!

Project Links:

NuGet Package: https://www.nuget.org/packages/MCPInvoke/1.0.0 (Link will be active once published)
GitHub Repository: https://github.com/grparry/MCPInvoke