MCP Smoke – test MCP servers using plain English commands
1–4 of 4 posts
Re: MCP Smoke – test MCP servers using plain English commands
#2When building MCP-based platforms, testing usually means manually crafting JSON-RPC requests or writing custom clients.
I built MCP Smoke as a lightweight test harness where you can:
Send real MCP requests using plain English Simulate real user/agent interactions Test tools, prompts, and resources end-to-end Plug in API keys and hit actual MCP servers
It’s useful if you're building MCP platforms and want:
Faster iteration during development Realistic testing instead of mocked flows Observability/analytics on how your MCP server behaves
Would love feedback on what kind of test scenarios or validations should be added.
Re: MCP Smoke – test MCP servers using plain English commands
#3When building MCP-based platforms, testing usually means manually crafting JSON-RPC requests or writing custom clients. I built MCP Smoke as a lightweight test harness where you can: Send real MCP requests using plain English Simulate real user/agent interactions Test tools, prompts, and resources end-to-end Plug in API keys and hit actual MCP servers It’s useful if you're building MCP platforms and want: Faster iter…
Nice job! Do you plan to implement some Evals automation to this too?
Re: MCP Smoke – test MCP servers using plain English commands
#4When building MCP-based platforms, testing usually means manually crafting JSON-RPC requests or writing custom clients. I built MCP Smoke as a lightweight test harness where you can: Send real MCP requests using plain English Simulate real user/agent interactions Test tools, prompts, and resources end-to-end Plug in API keys and hit actual MCP servers It’s useful if you're building MCP platforms and want: Faster iter…
Nice job! Do you plan to implement some Evals automation to this too?
I am not sure about this , should i?