IV. Troubleshooting

Localhost refused connection / MCP server won't start

If the MCP server does not start and you see localhost refused connection error when accessing http://localhost:9090/health, Windows may be blocking the server script execution.

Try this:

1. Confirm that http://localhost:9090/health returns a healthy result when you manually start an MCP Server by entering this line in command prompt:

   npx -y @elgato/mcp-server@latest --http

2. If Windows shows a permission or security prompt, allow it

3. Disable any option that forces Windows to ask every time, if appropriate

4. Try again from Streamer.bot

If the script execution is blocked, Streamer.bot may fail silently because it cannot launch the script in the background.

Nothing happens when I trigger an action

• Check if the MCP server is running by opening this page in the browser - http://localhost:9090/health. It should return the following message:

  {"status":"ok","AppConnected":true}

  If you didn't get that, just rerun the MCP server by right clicking the Streamer.bot Started trigger in Stream Deck MCP action then click Test Trigger

• Check that actionInput matches a valid Title or ID

• Refresh actions using RefreshExecutableActions

My button is not found

• Ensure the button exists in the MCP Actions page
• Refresh the action list via RefreshExecutableActions
• Verify the Title or ID is correct

Plugin action doesn’t work

• Some plugins may not fully support MCP
• Try triggering the button manually in Stream Deck
• Check if the plugin requires focus or specific conditions

New buttons are not showing

• Run RefreshExecutableActions
• Check Global Variables for new [SD] entries

Support

If you have issues that weren't addressed here, you can report them through the following:

• Open a support forum in my Discord Server
• Opening an issue in the Issues page