How do we handle non-TS mcp servers

[rodincave]

Many companies will have already built an MCP server in python, go, etc that they will use for their ChatGPT / MCP app. What is the best way to handle this ?

Example: https://github.com/datagouv/datagouv-mcp built in python

[fredericbarthelet]

Interesting question :)

The skybridge/web package currently adresses needs of developers building widgets in React. If they are using React as a frontend rendering engine, they can benefit from the utilities inside the package from day 1, whatever their MCP server code base is written in.

But maybe your question was larger than this? We could transpose the question in traditional web:

My API is written in Python using FastAPI. How should I build my frontend application?

There are 2 answers to this:

• use MVC (Model View controller) where the View part would be implemented in SSR (Server Side Rendering) on your backend. TMK, it's the old way of doing things. Templating engine tailored to the backend runtime could be use to render HTML/CSS code with the addition of minimal reactivity thanks to things like jQuery. In this category you had templating engine like twig or blade for PHP, Jinja for Python or thymeleaf for Java. I'd recommend against investing in that direction.
• use a standalone React application, my initial point. This setup could be complemented with a contract-enforced interface using a third party lib like pact. I have no specific idea yet if we could complement somehow the dev environment for people going that way. If there is time to invest at a later stage, I'd look at that typology of projects first

In addition to people not writing their MCP servers in Typescript, you also need to accommodate and account for developers that won't rely on React to build their widgets. Main alternatives being Remix, Vue, Angular, Solid and Svelte.

[fredericbarthelet]

The current discussion conclusion:

• we do not ship anything on non-TS runtimes
• on environments where all the frontend should be handled by skybridge, there is an additional dev required to boot a Vite dev server distinct from the MCP server process
• on environments where only the hooks are used but rendering of the frontend React components is handle directly in the backend process, there is nothing more to do

In order to better scope the work that'd be necessary to support option 2, we proceed with experimentation on one example project with a FastMCP pythong backend with at least 2 hooks rendering 2 different widgets written using exported mountWidget API

In the future, we'll need to measure if:

• companies will want to stick with their preferred runtime in the MCP server when not NodeJS even for ChatGPT App developments
• companies will develop multiple MCP servers (one for MCP normal use and one for ChatGPT App / MCP App)