MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

webcomponents-mcp-server

Earlier Revision Publisher unverified Confidence: Good (0.85)

webcomponents-mcp-server is an MCP server published by UI5, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does webcomponents-mcp-server support the current MCP specification (2026-07-28)?

Not yet confirmed. webcomponents-mcp-server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is webcomponents-mcp-server a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for webcomponents-mcp-server (as of 2026-08-20).

How do I connect to webcomponents-mcp-server?

webcomponents-mcp-server is available via the package npm:@ui5/webcomponents-mcp-server, the official MCP Registry under io.github.UI5/webcomponents-mcp-server, the source repository at https://github.com/ui5/webcomponents-mcp-server. Authentication: unknown. Transports: stdio.

Does webcomponents-mcp-server support MCP revision 2025-11-25?

Yes. webcomponents-mcp-server supports MCP revision 2025-11-25 (checked 2026-08-20).

Does webcomponents-mcp-server support MCP revision 2026-07-28?

No. webcomponents-mcp-server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were webcomponents-mcp-server's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

MCP server for UI5 Web Components development assistance

Which MCP spec revisions does webcomponents-mcp-server support?

webcomponents-mcp-server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is webcomponents-mcp-server?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for webcomponents-mcp-server

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
19
Forks
2
Last pushed
(46 days ago)
Created
Open issues
8
Primary language
TypeScript
License (repository)
Apache-2.0
Continuous integration
Present
Tests
Present
Security policy
None

Declared topics: agenticai, open-source, ui5, ui5-webcomponents, web-component, webcomponent — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
0.1.2
Last published
First published
Releases
3
License (package)
Apache-2.0
Maintainers
1
Direct dependencies
2
Unpacked size
532 KB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.UI5/webcomponents-mcp-server at version 0.1.2 - lists package npm:@ui5/webcomponents-mcp-server and repository https://github.com/ui5/webcomponents-mcp-server - accessed
  2. npm registry metadata for @ui5/webcomponents-mcp-server at published version 0.1.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed