Add MCP Apps support alongside MCP-UI #107
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implements MCP server icons at the correct architectural level (server initialization) instead of at the tool level. Adds both light and dark theme variants of the Mapbox logo using base64-encoded SVG data URIs. - Add mapbox-logo-black.svg for light theme backgrounds - Add mapbox-logo-white.svg for dark theme backgrounds - Update server initialization to include icons array with theme property - Use 800x180 SVG logos embedded as base64 data URIs This replaces the previous incorrect approach of adding icons to individual tools, which was not aligned with the MCP specification. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Updates the MCP SDK from 1.25.1 to 1.25.2 and recreates the output validation patch for the new version. The patch continues to convert strict output schema validation errors to warnings, allowing tools to gracefully handle schema mismatches. Changes: - Update @modelcontextprotocol/sdk from ^1.25.1 to ^1.25.2 - Recreate SDK patch for version 1.25.2 - Remove obsolete 1.25.1 patch file - All 397 tests pass with new SDK version Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Implement the MCP Apps pattern for static_map_image_tool, maintaining backward compatibility by supporting both patterns simultaneously. Changes: - Add _meta.ui.resourceUri to static_map_image_tool response for MCP Apps pattern - Create StaticMapUIResource (ui:// scheme) for static map previews - Register StaticMapUIResource in resourceRegistry.ts The MCP Apps pattern enables broader client compatibility (Claude Code, VS Code) while preserving existing MCP-UI functionality. The tool now returns both: 1. MCP-UI resource content via createUIResource() 2. MCP Apps metadata via _meta.ui.resourceUri This graceful degradation allows clients to use whichever pattern they support. Related: https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/ All tests passing (582 tests).
Contributor
Author
|
Closing this PR - MCP Apps support doesn't make sense for static_map_image_tool since it returns an image (base64 data), not a URL. The tool already includes the image in the response and MCP-UI handles iframe display. MCP Apps is better suited for tools that return URLs as primary content (like the devkit tools: preview_style_tool, style_comparison_tool, geojson_preview_tool). Focusing on mcp-devkit-server PR #62 for MCP Apps support instead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements the MCP Apps pattern for static_map_image_tool, maintaining backward compatibility by supporting both patterns simultaneously.
Changes
Tool with MCP Apps Support
Implementation Details
The tool now returns both:
createUIResource()(existing pattern)_meta.ui.resourceUrifield (new pattern)New UI resource created (ui:// scheme):
StaticMapUIResource- Serves HTML for static map previewClient Compatibility
This graceful degradation approach supports:
_meta.ui.resourceUri_meta.ui.resourceUricreateUIResource()Testing
All tests passing: 582 tests
Build verified successfully.
Related