Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@material-web-mcp Generate a Material Web button template"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server providing programmatic access to Material Web documentation for AI agents (Claude, Cursor, Cline, Copilot, etc.).
Requirements: Node.js >= 18.17
Connect to AI agents using npx (no installation required):
{
"mcpServers": {
"material-web": {
"command": "npx",
"args": ["-y", "material-web-mcp"]
}
}
}Related MCP server: MUI MCP Server
list_components: Returns JSON array of available Material Web components.
search_docs: Searches documentation for keywords (input: keyword string), returns matching paths with excerpts.
health_check: Verifies server uptime and documentation accessibility.
get_component_doc: Fetches full documentation for a specific component (input: component name).
get_theming_docs: Returns theming documentation for Material Web.
get_installation_docs: Returns installation and quick-start documentation.
generate_template: Generates basic HTML templates with Material Web components based on prompts (input: prompt string).
validate_website: Validates HTML code for correct Material Web component usage (input: HTML string).
Contributing Guide - How to contribute
Changelog - Version history
git clone https://github.com/shantoislamdev/material-web-mcp.git
cd material-web-mcp
npm install
npm test
npm startReturns the full documentation for a specific Material Web component
Inputs: component (required). Returns: documentation
Returns the installation and quick-start documentation for Material Web
Inputs: no named parameters. Returns: documentation
Returns the theming documentation for Material Web
Inputs: no named parameters. Returns: documentation
Performs a health check on the server, verifying uptime, documentation accessibility, and basic functionality
Inputs: no named parameters. Returns: errors, status, uptime, docsCount, +2 more
Returns a JSON array of available Material Web component names
Inputs: no named parameters. Returns: components
Searches Material Web documentation for a keyword and returns matching file paths with excerpts
Inputs: keyword (required). Returns: results
Validates HTML code for correct Material Web component usage
Inputs: html (required). Returns: valid, errors, warnings
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool targets a distinct purpose: documentation retrieval for theming, installation, components, plus listing, searching, health checking, and validation. There is no overlap between tool responsibilities.
Most tools follow a clear verb_noun pattern (get_*, list_*, search_*, validate_*), but health_check is a noun phrase rather than check_health. This minor inconsistency is the only deviation from an otherwise uniform convention.
Seven tools provide a focused and well-scoped set for a documentation and validation server. Each tool earns its place, and the count is neither too sparse nor overwhelming.
The domain—Material Web documentation and HTML validation—is fully covered: installation and theming docs, component listing and retrieval, documentation search, and validation. No obvious gaps exist for the intended read-only and analysis purposes.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Serves your design system and coding standards to coding agents, so they stop guessing.
Web search and page reading for AI agents, including JSON APIs, RSS feeds and YouTube.
Provides access to Google's public developer documentation.
