Skip to content

Conversation

xiehust
Copy link

@xiehust xiehust commented Mar 8, 2025

I've successfully fixed the bug in the mcp-browser-automation tool. Here's what was done:

Identified the issue: The handleToolCall function in toolsHandler.ts was returning an incorrect response structure. It was wrapping the response in a toolResult object, but the MCP SDK expected the content directly.

Fixed the issue: Modified the function signature and all return statements to remove the nested toolResult wrapper. Changed:

Promise<{ toolResult: CallToolResult }>
to:

Promise
And similarly updated all return statements to return the content directly.

Installed dependencies and built the project:

npm install
Tested the fix by successfully:

Navigating to the Amazon deals page
Taking a screenshot (saved to your Downloads folder)
Closing the browser
The MCP browser automation tool is now working correctly and can be used to browse websites, take screenshots, and perform other browser actions as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant