turbomcp and mcp-probe

One project is a full-featured MCP SDK for building enterprise-grade integrations, while the other is an MCP client library and debugging toolkit that also provides a production-ready SDK for integrations and a core architecture for interactive tools, suggesting they are ecosystem siblings with potentially overlapping SDK functionalities but distinct primary focuses.

turbomcp
52
Established
mcp-probe
42
Emerging
Maintenance 10/25
Adoption 9/25
Maturity 15/25
Community 18/25
Maintenance 6/25
Adoption 10/25
Maturity 15/25
Community 11/25
Stars: 74
Forks: 15
Downloads:
Commits (30d): 0
Language: Rust
License: MIT
Stars: 115
Forks: 10
Downloads:
Commits (30d): 0
Language: Rust
License: MIT
No Package No Dependents
No Package No Dependents

About turbomcp

Epistates/turbomcp

A full featured, enterprise grade rust MCP SDK

This project helps Rust developers build "Model Context Protocol (MCP)" servers and clients. It takes your Rust functions and structures, automatically converting them into network-accessible tools, resources, and prompts. Developers can use this to create robust, production-ready services that communicate using the MCP standard, potentially integrating with platforms like Claude Desktop or other AI tools.

Rust-development API-development backend-services protocol-implementation microservices

About mcp-probe

conikeec/mcp-probe

A Model Context Protocol (MCP) client library and debugging toolkit in Rust. This foundation provides both a production-ready SDK for building MCP integrations and the core architecture for an interactive debugger.

This tool helps developers working with Model Context Protocol (MCP) servers to debug, test, and interact with them efficiently. It takes in MCP server connections (HTTP/SSE, WebSocket, STDIO, TCP) and outputs real-time protocol analysis, interactive capability browsing, and tool execution results. The primary users are developers, integrators, and operations engineers responsible for building, maintaining, or debugging MCP-based systems.

API-debugging protocol-testing integration-development backend-troubleshooting server-interaction

Scores updated daily from GitHub, PyPI, and npm data. How scores work