MCP Validation

[GoatedChopin]

Hey, I'm making a quick (low-quality) post away from my dev machine.

I built a few toy projects with this framework because I thought it looked cool and wanted to try Dioxus anyway.

One of those toy projects was a browser-use MCP server to help some of my AI agents use Playwright. I found that using the Forge MCP macro did create and expose an MCP API, but when I added the localhost MCP URL to Claude Code and Cursor, neither app was able to detect the tools nor use them.

After a good deal of debugging, I was able to solve this by adding a compatibility layer (Node.js script) between Cursor and the Forge MCP API to change the structure of the "tools" response body before it reaches Cursor.

I don't want to assume that this extra work / compatibility layer is an error on the Forge side, so I thought I'd ask a couple of questions:

1. Have you used forge apps as MCP servers for Cursor / Claude Code and, if so, what did your config look like to make that work without a compatibility layer?

2. If not Cursor / Claude Code, have you tested the MCP functionality with any tools in particular?

I'm happy to provide code and config examples to explain the issue I was seeing on my end with the MCP when I'm back at my computer. Forge seems very promising and I'm eager to get a real application working end-to-end.

Thanks,
-Colby