Nice! I was looking for something like that myself.
Going forward, I’m only going to maintain and update the remote http based MCP server. If your client doesn’t support remote servers yet, you can use
{
"mcpServers": {
"Vaadin": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vaadin-mcp.fly.dev/mcp",
"--transport http-only"
]
}
}
}
Yes, Markdown format makes integration with LLM much easier. In our project we first run docs through Pandoc for unification and then feed them into Context7.
Hey @marcushellberg,
Great effort and thank you so much for creating and maintaining the MCP server.
I wanted to try it using Gemini CLI. I added the Vaadin MCP server to my settings.json as it is described in the Gemini CLI docs:
{
"ideMode": true,
"selectedAuthType": "oauth-personal",
"theme": "Default",
"hasSeenIdeIntegrationNudge": true,
"mcpServers": {
"Vaadin": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vaadin-mcp.fly.dev/mcp",
"--transport http-only"
]
}
}
}
Gemini recognizes the Vaadin MCP server, but it seems to be offline or disconnected:
Do you may have an idea why it is not property recognized?
Sorry, my bad. I have to add it like this:
{
...
"mcpServers": {
"Vaadin": {
"httpUrl": "https://vaadin-mcp.fly.dev/mcp"
}
}
}
That’s weird. I have this settings for Gemini and it’s working fine:
{
"selectedAuthType": "oauth-personal"
,
"mcpServers": {
"Vaadin": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vaadin-mcp.fly.dev/mcp",
"--transport http-only"
]
}
}
}
Thanks a lot for setting this up! I have been using it the past few weeks and it was a great help.
Yesterday, I noticed that it got disconnected and it seems like the domain vaadin-mcp.fly.dev is not available anymore. Is it just me or a problem with fly.dev/fly.io?