MCP Server for Vaadin
- Vaadin MCP Server
- Getting Started
- What the Hosted Server Runs
- Supported Tools
- Running Your Own Server
- Transport Types
- Resources
Model Context Protocol (MCP) is an open standard that enables AI assistants to securely integrate with external data sources and tools. It allows AI development tools like Claude Code, Cursor, GitHub Copilot, and others to access structured information from external sources.
Vaadin MCP Server
Vaadin provides an MCP server that gives AI assistants direct access to comprehensive Vaadin documentation. This enables AI assistants to provide accurate, context-aware responses based on latest Vaadin documentation.
|
Important
|
This is the Vaadin documentation MCP server at |
The Vaadin MCP server provides:
-
Semantic search across Vaadin documentation
-
Full document retrieval for complete context
-
Component version information and API references
-
Component-specific API documentation (Java, React, Web Components)
-
Component styling and theming information
-
Support for both Java and React applications
-
Current Vaadin version information
-
Vaadin development primer with best practices
Getting Started
To use the Vaadin MCP server with your AI development tool, follow these steps:
-
Choose your AI development tool from the supported tools list
-
Follow the configuration instructions for your specific tool
-
Restart your tool to load the MCP server
-
Start asking questions about Vaadin development
The MCP server automatically provides your AI assistant with access to up-to-date Vaadin documentation.
|
Tip
|
If you use Claude Code or Codex, the Vaadin Agent Marketplace is the quickest way to get started. A single plugin installs both the Vaadin MCP server and a set of Vaadin development skills, so there’s no need to configure the MCP server by hand. See the setup guides for Claude Code and Codex for details. |
|
Tip
|
Documentation lookup is one half of what an agent needs. The other half is knowing whether the code it wrote actually runs. The Dev Loop CLI gives an agent a single command that makes its edits live in the running application and reports the result as an exit code, along with a set of skills that teach it how to use them. The two are designed to be used together, and the Dev Loop Tutorial sets up both. |
What the Hosted Server Runs
Three facts about mcp.vaadin.com, for anyone whose organization asks where their documentation queries go:
-
It runs in the EU. Requests are served from EU-hosted infrastructure.
-
Tool calls are reported to Amplitude, so that Vaadin can see which tools are actually used. Your question is never sent — a report carries the tool’s name, how long the call took, and how long the question was.
-
No record is kept of individual queries. The server is able to log every call it answers, and that logging is switched off on the hosted service.
Supported Tools
The Vaadin MCP server is compatible with various AI development tools. Each tool has different configuration requirements and transport support.
See the MCP Setup Guide for detailed configuration instructions for:
Running Your Own Server
Vaadin’s hosted server is the one to point your tools at unless your organization can’t send documentation queries to a service outside its own network. For those cases the same server ships as a container image you run yourself: it needs no network at runtime, it can record every tool call to an audit log, and it reports nothing back to Vaadin. Running it requires a commercial Vaadin subscription, where the hosted server does not.
It’s the same server, not a cut-down edition: the image published to Docker Hub is the one mcp.vaadin.com runs, so your own instance answers from the same code and the same documentation. Only the three settings above differ. See Self-Hosting the MCP Server.
Transport Types
|
Important
|
The Vaadin MCP server uses HTTP transport (streamable-http). This is natively supported by Claude Code, Cursor, Windsurf, GitHub Copilot (VS Code and JetBrains IDEs), Codex, and Gemini CLI. For stdio-only tools like Junie, you can use @pyroprompts/mcp-stdio-to-streamable-http-adapter as a bridge between the two transport types. |