Robot Framework rf-mcp support

[laguill]

Hello

I tried to add rf-mcp to toolhive but I cannot make it work with LM Studio nor toolhive playground.

Here is a link to the github repo https://github.com/manykarim/rf-mcp

Here is what I tried

• Setup rf-mcp with toolhive

thv run ghcr.io/manykarim/rf-mcp:latest

• Write code

Then I tried Ministral 3 3B on LM studio

Use #robotmcp to create a TestSuite and execute it step wise.
Create a test for https://www.saucedemo.com/ that:
- Logs in to https://www.saucedemo.com/ with valid credentials
- Adds two items to cart
- Completes checkout process
- Verifies success message

Use Browser Library.
Execute the test suite stepwise and build the final version afterwards.

The tool seams to fail but I don't understand what is wrong

2026-02-09 17:38:34 [ERROR]
 [Plugin(mcp/manykarim-rf-mcp)] stderr: _0x243630 [Error]: SSE error: Non-200 status code (405)
    at _eventSource.onerror (C:\Users\g.lafon\AppData\Local\Programs\LM Studio\resources\app\.webpack\lib\mcpbridgeworker.js:29:217128)
    at _0x3ba527._0x245a1d (C:\Users\g.lafon\AppData\Local\Programs\LM Studio\resources\app\.webpack\lib\mcpbridgeworker.js:29:359571)
    at C:\Users\g.lafon\AppData\Local\Programs\LM Studio\resources\app\.webpack\lib\mcpbridgeworker.js:29:353226
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  code: 405,
  event: {
    type: 'error',
    message: 'Non-200 status code (405)',
    code: 405,
    defaultPrevented: false,
    cancelable: false,
    timeStamp: 30384.1011
  }
}

[jerm-dro]

Hi @laguill can you provide some debugging information?

1. Using thv list --all you should be able to see the name of your server and its high-level health. Is it healthy?
2. If not healthy, run thv status $yourServerName to collect more details.
3. Run thv logs $yourServerName to get the logs from the backend.
4. Run thv logs $yourServerName to get the logs from the proxy.

[jerm-dro]

To clarify, the manykarim-rf-mcp has a separate endpoint which exposes a UI for debugging it, and you want to expose this UI on a different port?

If I understand correctly, your command seems like it's nearly there:

thv run --name manykarim-rf-mcp `
   --transport streamable-http `
   --target-port 8002 `
   ghcr.io/manykarim/rf-mcp:latest `
   -- --host 0.0.0.0 --port 8002 --debugPort 8003

Everything beyond the -- gets passed to the backend directly. Assuming manykarim-rf-mcp supports a CLI arg for configuring debugPort, the above should work. I'm not aware of anything thv would do that would prevent the backend from exposing another port.

[laguill]

Yes the frontend is exposed on a different port.

The podman command is working I cannot make it work witj thv cli.

podman run -d `
  --name manykarim-rf-mcp `
  -p 8002:8000 `
  -p 8003:8001 `
  ghcr.io/manykarim/rf-mcp:latest

thv run --name manykarim-rf-mcp `
  --transport streamable-http `
  --target-port 8002 `
  --publish 8003:8001 `
  ghcr.io/manykarim/rf-mcp:latest `
  -- --host 0.0.0.0 --port 8002

The frontend port is not forwarded

podman ps | grep manykarim-rf-mcp
0450ec0ada1f  ghcr.io/manykarim/rf-mcp:latest           --host 0.0.0.0 --...  28 minutes ago  Up 28 minutes  127.0.0.1:63713->8002/tcp, 8000-8001/tcp        manykarim-rf-mcp

[jerm-dro]

Ok, yes that's a gap in thv functionality. No --publish flag exists or something that would behave similarly. Without such a flag, thv will not expose the port in podman/docker.

I've filed an issue to track this enhancement here: #3812

[jerm-dro]

@laguill If you don't have other questions here, let's move the discussion over to that issue. Then, I'll close this thread.