Can't figure out if there is a way to mock a server with HTTP transport

[pjsg]

I'd like to use mcp mock to define a bunch of tools, and then, somehow, assemble them so that I can use them via mcp proxy so that I can prototype/test an application without needing to write a whole bunch of code.

Am I missing something, or is this not possible today?

[stefanstranger]

Is there a reason you want to use them via mcp proxy? I just configure them in my MCP Host configuration.

[pjsg]

I was hoping to use the proxy so that I could stand up a dummy MCP service in a docker container (so I could deploy it into kubernetes so that the rest of the team could continue their work). My approach is to develop a dummy MCP service and then work on the LLM side to figure out which tools it needs to solve the problem that I'm working on, and be able to iterate rapidly. The real service will be deployed with HTTP transport.

[stefanstranger]

Is the approach I showed helpful? Not sure to be honest...

[pjsg]

Yes it is. I was unaware of the mcp_omni_connect package. Thank you. Philip Gladstone [image: Bitsight website] <https://pskreporter.info>

…

On Thu, May 29, 2025 at 11:03 AM Stefan Stranger ***@***.***> wrote: *stefanstranger* left a comment (f/mcptools#55) <#55 (comment)> Is the approach I showed helpful? Not sure to be honest... — Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALQLTPRDXFYAJPEZV3EAKT3A4OT3AVCNFSM6AAAAAB6DGD6UOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJZGY4DGNJVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pjsg]

I was originally confused by this section of the README.md [image: image.png] Assuming that you have to run the `mcp proxy start` before you can run `mcp tools localhost:3000` this indicates that it should produce some output. In fact it says `Error: failed to connect to SSE stream: Get "localhost:3000": unsupported protocol scheme "localhost"`. Also, the `mcp proxy start` does not listen on port 3000 as it seems to only do stdio transport. Maybe this just requires a documentation change to change `mcp tools localhost:3000` to `mcp tools mcp proxy start` and that does work. It may also be worth mentioning that, in order to provide a mock mcp server over http. you have to use another software package (e.g. the `mcp_omni_connext` package). In any event, I want to thank the authors for putting this together as it is very helpful. Philip Gladstone [image: Bitsight website] <https://pskreporter.info> On Thu, May 29, 2025 at 11:34 AM Philip Gladstone < ***@***.***> wrote:

…

Yes it is. I was unaware of the mcp_omni_connect package. Thank you. Philip Gladstone [image: Bitsight website] <https://pskreporter.info> On Thu, May 29, 2025 at 11:03 AM Stefan Stranger ***@***.***> wrote: > *stefanstranger* left a comment (f/mcptools#55) > <#55 (comment)> > > Is the approach I showed helpful? Not sure to be honest... > > — > Reply to this email directly, view it on GitHub > <#55 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AALQLTPRDXFYAJPEZV3EAKT3A4OT3AVCNFSM6AAAAAB6DGD6UOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJZGY4DGNJVGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[f]

Maybe I should consider updating README to make it less confusing :)