MCP testing was painful. So I fixed it

announcements
1

Three months ago, I was building AI applications with the Model Context Protocol (MCP). The official inspector worked... technically. But as someone who lives in the terminal and thinks in JSON, I kept hitting walls.

Context switching between IDE → browser → forms → copy-paste → repeat was killing my flow.

So I built MCP Probe 🎯

What makes it different:

• Terminal-native TUI (because some of us never left vim)

• Fuzzy search through 300+ tools in milliseconds

• Real-time parameter validation with guided forms

• Response viewer with multiple formats (JSON, tree, formatted)

• Works offline (revolutionary, I know)

• Pure Rust → single binary, zero dependencies

#install
curl -fsSL https://raw.githubusercontent.com/conikeec/mcp-probe/master/install.sh | bash

#brew
# Add the tap
brew tap conikeec/tap

# Install mcp-probe
brew install mcp-probe

# Or in one command
brew install conikeec/tap/mcp-probe

#cargo
cargo install mcp-cli

But here's the kicker: It's not just a debugger. It's a full SDK.

use mcp_core::client::McpClient;
// Build your own MCP automation
let client = McpClient::new(transport).await?;
for tool in client.list_tools().await? {
if tool.name.contains("github") {
// Automate all the things
 }
}

MCP Probe is live on GitHub, crates.io, and Homebrew. The terminal-native future of MCP debugging starts now.

Who else thinks debugging tools should match your development workflow, not fight it?

2 Likes