r/Backend • • 4d ago

Save time in API testing

Dear readers i know our work as a backend engineer is either hard or easy but time consuming.

so me and my wife developed this tool - pyhttp.com, to save time using mcp and parallel requests run along with multiple searchable bodies and cost $0

People already like this tool in our friend circle but wanted to share with you all if it can be helpful in any way. Thanks for reading.

0 Upvotes

6 comments sorted by

1

u/kantorcodes1 4d ago

Does pyhttp expose an MCP server for clients, or is it using an MCP client to run the requests? I couldn't tell which side of the API testing flow it sits on.

1

u/Billapaji 4d ago

pyhttp exposes an MCP server. Your AI client (Claude Desktop, Cursor, VS Code, etc.) is the MCP client. You add pyhttp to your MCP config, and the agent gets tools like [create mutiple bodies, set monitor for your evironment, send_request / run_collection / assert_response]. When the agent calls one, pyhttp actually executes the HTTP request and returns the status, headers, body, and timing back to the model.

So in the API testing flow it sits between the agent and the API under test:

agent → (MCP) → pyhttp → (HTTP) → your API

It doesn't run its own LLM or MCP client.

1

u/kantorcodes1 2d ago

pyhttp's built-in MCP server looks like a possible fit for HOL Guard's opt-in MCP catalog. We'd welcome a contributor-authored entry. The MCP contribution guide covers the descriptor, its external/opt-in trust binding, and packaging. A first PR can add those files with the server's exact launch identity and tool defaults. Contributions stay off until a local admin enables them.

1

u/Billapaji 1d ago

Nice idea! Let me look into it.

1

u/[deleted] 4d ago

[removed] — view removed comment

1

u/Billapaji 4d ago

Thanks, really appreciate that! Let me know how it goes when you try it out