Docs MCP Server

by vaadin Your server? Claim it

not responding

Docs MCP is listed as active in the registry but did not answer our last check. It exposes 11 tools.

Provides Vaadin Documentation and help with development tasks

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

171 ms

Response time

average over 24h

open, no key

Access

streamable-http

Docs MCP does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add docs-mcp --transport http https://mcp.vaadin.com/docs/

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

component

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').

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').

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').

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').

vaadin

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-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.

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.), 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.

components

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.

full

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).

latest

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}.

supported

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.

theme

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 all themes.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.vaadin.com/docs/	streamable-http	answering	171 ms	5 min ago

Alternatives to Docs MCP

same job, measured the same way

MCP Devkit Server

by mapbox

Provides AI assistants with direct access to Mapbox developer APIs and documentation.

249 installs/wk answering

Googleapis

by googleapis-developerknowledge

Provides access to Google's public developer documentation.

3 tools answering

MCP Victorialogs

by victoriametrics

MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation

local only

MCP Victorialogs

by victoriametrics-community

MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation

local only

MCP Victoriatraces

by victoriametrics-community

MCP Server for VictoriaTraces. Provides integration with VictoriaTraces API and documentation

local only

Avalara Developer Documentation

by avalara

Provides access to Avalara developer documentation, integration guides, and code examples

answering

MCP Victoriametrics

by victoriametrics-community

MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation

local only

MCP Victoriametrics

by victoriametrics

MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation

local only

Docs MCP — questions

Answers built from our own checks of this server.

What can Docs MCP do?

It exposes 11 tools, read directly from the server on our last check. Among them: get_component_java_api, get_component_react_api, get_components_by_version, get_component_styling, get_component_web_component_api, get_full_document and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Docs MCP mostly used for?

Its tools cluster around component and vaadin. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Docs MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 171 ms. The bar chart above shows every period we have measured.

Is Docs MCP still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Docs MCP as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Docs MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Docs MCP need an API key?

No. Docs MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.