🚀 Vaadin MCP Server

Add the Vaadin MCP server to your project or global configuration.

{
  "mcpServers": {
    "vaadin": {
      "type": "http",
      "url": "https://mcp.vaadin.com/docs"
    }
  }
}

File locations:

• Project-scoped: .mcp.json (in project root)
• Global: ~/.claude.json

Add the Vaadin MCP server to your project or global configuration.

{
  "mcpServers": {
    "vaadin": {
      "type": "http",
      "url": "https://mcp.vaadin.com/docs"
    }
  }
}

File locations:

• Project-scoped: .cursor/mcp.json
• Global: ~/.cursor/mcp.json

Add the Vaadin MCP server through Windsurf Settings (bottom right) or Cmd+Shift+P → "Open Windsurf Settings".

{
  "mcpServers": {
    "vaadin": {
      "type": "http",
      "url": "https://mcp.vaadin.com/docs"
    }
  }
}

Junie only supports stdio-based MCP servers. Use @pyroprompts/mcp-stdio-to-streamable-http-adapter to bridge stdio to the HTTP-based Vaadin MCP server.

1. Open IDE settings: Ctrl+Alt+S (Windows/Linux) or Cmd+, (macOS)
2. Navigate to Tools → Junie → MCP Settings
3. Click the Add button and add the configuration below

{
  "mcpServers": {
    "vaadin": {
      "command": "npx",
      "args": ["@pyroprompts/mcp-stdio-to-streamable-http-adapter"],
      "env": {
        "URI": "https://mcp.vaadin.com/docs",
        "MCP_NAME": "vaadin"
      }
    }
  }
}

File locations:

• Project-scoped: .junie/mcp/mcp.json
• Global: ~/.junie/mcp.json

⚠️ Important: MCP servers only work when GitHub Copilot is used in Agent mode. Regular Copilot Chat does not support MCP.

Agent mode with MCP support is now in public preview for JetBrains IDEs (as of May 2025).

1. Create .copilot/mcp-config.json in your project root (JetBrains IDEs use the same format as VS Code)
2. Add the configuration below
3. Switch to Agent mode: Click the GitHub Copilot icon → Change to Agent mode
4. Configure MCP servers: Click Tools icon → Add More Tools → Edit mcp.json
5. Alternative: Click GitHub Copilot icon → Edit settings → MCP Servers section

{
  "servers": {
    "vaadin": {
      "url": "https://mcp.vaadin.com/docs"
    }
  }
}

Learn more:

• GitHub Copilot MCP Guide
• JetBrains MCP Announcement

⚠️ Important: MCP servers only work when GitHub Copilot is used in Agent mode. Regular Copilot Chat does not support MCP.

Requires VS Code 1.99 or later.

1. Create .vscode/mcp.json in your project root
2. Add the configuration below
3. Click the Start button that appears at the top of the MCP servers list
4. Switch to Agent mode: Open Copilot Chat → Click mode selector → Select "Agent"
5. Click the tools icon in Agent mode to view available MCP servers

{
  "servers": {
    "vaadin": {
      "type": "http",
      "url": "https://mcp.vaadin.com/docs"
    }
  }
}

Learn more:

• VS Code MCP Documentation
• GitHub Copilot MCP Guide

Add the Vaadin MCP server to your Codex configuration. Works with both Codex CLI and IDE extension.

1. Open or create ~/.codex/config.toml
2. Add the server configuration below
3. Restart Codex to load the new MCP server

[mcp_servers.vaadin]
url = "https://mcp.vaadin.com/docs"

Learn more:

• Codex MCP Documentation
• Codex GitHub Repository

Add the Vaadin MCP server to your Gemini CLI configuration. Gemini will automatically use Vaadin documentation tools when relevant.

1. Open or create ~/.gemini/settings.json
2. Add the server configuration below
3. Restart Gemini CLI to load the new MCP server

{
  "mcpServers": {
    "vaadin": {
      "httpUrl": "https://mcp.vaadin.com/docs"
    }
  }
}

Learn more:

• Gemini CLI GitHub Repository
• Gemini CLI MCP Documentation

The Vaadin MCP server can be used with any MCP-compatible client. Choose the appropriate configuration based on your tool's transport support:

If your tool supports HTTP/SSE natively:

Simply point it to our HTTP endpoint:

https://mcp.vaadin.com/docs

The exact configuration format depends on your specific tool. Look for settings like "MCP Server URL", "HTTP transport", or "Streamable HTTP" in your tool's documentation.

If your tool only supports stdio:

Use an HTTP adapter to bridge stdio to HTTP. This works with any stdio-based MCP client:

{
  "mcpServers": {
    "vaadin": {
      "command": "npx",
      "args": ["@pyroprompts/mcp-stdio-to-streamable-http-adapter"],
      "env": {
        "URI": "https://mcp.vaadin.com/docs",
        "MCP_NAME": "vaadin"
      }
    }
  }
}

Adapt the JSON structure to match your tool's configuration format. The adapter uses environment variables: URI for the server endpoint and MCP_NAME as an identifier.