Quicker MCP

Model Context Protocol (MCP) implementation for software integration.

Architecture Overview

This project implements an MCP server that integrates with target software through DLL injection and provides HTTP API for external clients.

Components

1. Injection DLL (.NET): Injected into target software for direct interaction
2. MCP Server (.NET): HTTP API server that communicates with injected DLL
3. .NET SDK: Client library for easy integration

Communication Flow

Target Software ←→ Injected DLL ←→ Named Pipes ←→ MCP Server ←→ HTTP API ←→ External Clients

Technology Stack

• .NET 8: Main development platform
• ASP.NET Core: HTTP API server
• Named Pipes: Inter-process communication
• SignalR: Real-time communication (optional)
• C++/CLI: DLL injection code

Project Structure

quicker-mcp/
├── src/
│   ├── InjectionDll/          # DLL to be injected
│   ├── McpServer/             # HTTP API server
│   ├── McpSdk/                # .NET client SDK
│   └── Shared/                # Shared models and contracts
├── tests/
├── docs/
└── examples/

Development Setup

1. Install .NET 8 SDK
2. Clone the repository
3. Run dotnet restore to restore dependencies
4. Build the solution: dotnet build

Usage

Starting the MCP Server

cd src/McpServer
dotnet run

Using the SDK

using QuickerMcp.Sdk;

var client = new McpClient("http://localhost:5000");
var result = await client.ExecuteCommandAsync("some-command");

API Endpoints

• GET /api/status - Server status
• POST /api/execute - Execute commands
• GET /api/resources - List available resources
• POST /api/resources/{id} - Access specific resource

Security Considerations

• Use HTTPS in production
• Implement authentication/authorization
• Validate all input data
• Secure named pipe communication