Docs is an MCP server with 11 tools an agent can call, among them get_component_java_api, get_component_react_api, get_component_styling. It answers at https://mcp.vaadin.com/docs/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Provides Vaadin Documentation and help with development tasks
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_component_java_api | Returns the Java API documentation for a specific Vaadin component. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button'). Inputs: component_name, vaadin_version |
get_component_react_api | Returns the React API documentation for a specific Vaadin component. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button'). Inputs: component_name, vaadin_version |
get_component_styling | Returns the styling/theming documentation for a specific Vaadin component. Returns both Java and React styling documentation when available. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button'). Inputs: component_name, vaadin_version |
get_component_web_component_api | Returns the Web Component/TypeScript API documentation for a specific Vaadin component by fetching from external TypeScript API docs. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button'). Inputs: component_name, vaadin_version |
get_components_by_version | Returns a comprehensive list of components available in a specific Vaadin version, including component names, React component names, Java class names, and npm packages. Inputs: version |
get_full_document | Retrieves complete documentation pages for one or more file paths. Use this when you need full context beyond what search results provide. Provide file_paths only (array). Inputs: file_paths |
get_latest_vaadin_version | Returns the latest stable version of Vaadin as a simple JSON object. This is useful when setting up new projects, checking for updates, or when helping with dependency management. Returns: {version, released}. |
get_supported_vaadin_versions | Returns the latest stable release for each supported Vaadin major version (25, 24, 23, 14, 8, 7) with version number, release date, and whether it requires a commercial license. Useful for migration planning and understanding which versions |
get_theme_css_properties | Returns CSS custom properties documentation for a specific Vaadin theme (Aura, Lumo, or Base styles). Use this to look up the correct CSS variables for the theme the application is using. Base style properties (--vaadin-*) are available in Inputs: theme, vaadin_version |
get_vaadin_primer | IMPORTANT: Always use this tool FIRST before working with Vaadin. Returns a comprehensive primer document with current (2025+) information about modern Vaadin development. This addresses common AI misconceptions about Vaadin and provides up Inputs: vaadin_version |
search_vaadin_docs | Search Vaadin documentation for relevant information about Vaadin development, components, and best practices. Uses hybrid semantic + keyword search. USE THIS TOOL for questions about: Vaadin components (Button, Grid, Dialog, etc.), TestBen Inputs: question, vaadin_version, max_results, max_tokens, ui_language |
Every block below points at https://mcp.vaadin.com/docs/. Pick your client and copy.
claude mcp add --transport http docs https://mcp.vaadin.com/docs/
{
"mcpServers": {
"docs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.vaadin.com/docs/"]
}
}
}{
"mcpServers": {
"docs": {
"url": "https://mcp.vaadin.com/docs/"
}
}
}{
"servers": {
"docs": {
"type": "http",
"url": "https://mcp.vaadin.com/docs/"
}
}
}{
"context_servers": {
"docs": {
"url": "https://mcp.vaadin.com/docs/"
}
}
}{
"mcpServers": {
"docs": {
"serverUrl": "https://mcp.vaadin.com/docs/"
}
}
}{
"mcpServers": {
"docs": {
"url": "https://mcp.vaadin.com/docs/"
}
}
}name: Docs
version: 0.0.1
schema: v1
mcpServers:
- name: Docs
type: streamable-http
url: https://mcp.vaadin.com/docs/{
"mcpServers": {
"docs": {
"httpUrl": "https://mcp.vaadin.com/docs/"
}
}
}{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://mcp.vaadin.com/docs/"
}
}
}{
"mcpServers": {
"docs": {
"url": "https://mcp.vaadin.com/docs/"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.vaadin.com%2Fdocs%2F&type=streamable_http&id=docs&name=Docs
It answered our last check on 19 October 2026 in 123 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vaadin.com and served from mcp.vaadin.com, the vendor's own domain: https://mcp.vaadin.com/docs/.
11, as returned by the server's own tools/list on 11 September 2026: get_component_java_api, get_component_react_api, get_component_styling, get_component_web_component_api, get_components_by_version, get_full_document, get_latest_vaadin_version, get_supported_vaadin_versions, and 3 more.
It answered our last check on 19 October 2026 in 123 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.vaadin.com/docs/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.vaadin. Endpoint host: mcp.vaadin.com. ARD identifier: urn:air:com.vaadin:mcp:docs-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.