ZBS Index What actually exists in applied AI, with the source next to it

mcp server

docs-mcp

Provides Vaadin Documentation and help with development tasks

Description as published by the maintainer. Source

  • version 1.0.1
  • archived
  • documentation
  • document understanding

archived — The linked repository returns 404. It was deleted, renamed or made private. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

11 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

get_component_java_api(component_name, vaadin_version)
Returns the Java API documentation for a specific Vaadin component. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button'). Required: component_name, vaadin_version.
get_component_react_api(component_name, vaadin_version)
Returns the React API documentation for a specific Vaadin component. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button'). Required: component_name, vaadin_version.
get_component_styling(component_name, vaadin_version)
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'). Required: component_name, vaadin_version.
get_component_web_component_api(component_name, vaadin_version)
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'). Required: component_name, vaadin_version.
get_components_by_version(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. Required: version.
get_full_document(file_paths)
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). Required: 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 are available.
get_theme_css_properties(theme, vaadin_version)
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 all themes. Required: theme, vaadin_version.
get_vaadin_primer(vaadin_version)
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-to-date information about Java vs React development models, project structure, components, and best practices. Essential reading to avoid outdated assumptions. For legacy versions (7, 8, 14), returns guidance on version-specific resources. Required: vaadin_version.
search_vaadin_docs(question, max_tokens, max_results, ui_language, vaadin_version)
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.), TestBench, UI testing, unit testing, integration testing, @BrowserCallable, Binder, DataProvider, validation, styling, theming, security, Push, Collaboration Engine, PWA, production builds, Docker, deployment, performance, and any Vaadin-specific topics. When using this tool, try to deduce the correct development model from context: use "java" for Java-based views, "react" for React-based views, or "common" for both. Use get_full_document with file_paths containing the result's file_path when you need complete context. Required: question, vaadin_version.

Last successful function declaration observed on . Source: https://mcp.vaadin.com/docs/. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://mcp.vaadin.com/docs/.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 1.0.1 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2025-10-29 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2025-10-29 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status not_found GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. as of fetch GitHub
mcp tools declared 11 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe mcp.vaadin.com
mcp endpoint status ok The server listed 11 functions when asked. as of probe mcp.vaadin.com

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. vaadin/vaadin-documentation-services on GitHub — GitHub, observed , trust tier 3.
  2. Tools declared by the MCP server at https://mcp.vaadin.com/docs/ — mcp.vaadin.com, observed , trust tier 1.
  3. Official MCP Registry — Model Context Protocol, observed , trust tier 1.