@webspire/mcp 0.10.0 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +37 -15
- package/data/registry.json +149 -44
- package/dist/registration.js +128 -1
- package/dist/search.d.ts +9 -1
- package/dist/search.js +45 -0
- package/dist/types.d.ts +23 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,17 +1,6 @@
|
|
|
1
1
|
# @webspire/mcp
|
|
2
2
|
|
|
3
|
-
MCP server for [Webspire](https://webspire.de) — AI-native discovery of CSS snippets, UI patterns, canvas effects, page templates, and font recommendations. All Tailwind v4, token-based, dark mode, accessible.
|
|
4
|
-
|
|
5
|
-
## Stability Model
|
|
6
|
-
|
|
7
|
-
Webspire is intentionally iterative.
|
|
8
|
-
|
|
9
|
-
- Not every pattern or snippet is optimal yet.
|
|
10
|
-
- Registry contents, taxonomy, scoring, and composition output may change over time.
|
|
11
|
-
- The only guaranteed answer is the snapshot you receive when you make the request.
|
|
12
|
-
- This is by design: the registry is supposed to keep improving instead of acting like a fixed framework API.
|
|
13
|
-
|
|
14
|
-
The important invariant is different: MCP should provide context, discovery, and composition help, while the resulting code remains something you can own directly in your project. The goal is not to introduce a runtime dependency.
|
|
3
|
+
MCP server for [Webspire](https://webspire.de) — AI-native discovery of CSS snippets, UI patterns, canvas effects, page templates, motion recipes, and font recommendations. All Tailwind v4, token-based, dark mode, accessible.
|
|
15
4
|
|
|
16
5
|
## Quick Start
|
|
17
6
|
|
|
@@ -63,6 +52,14 @@ The important invariant is different: MCP should provide context, discovery, and
|
|
|
63
52
|
| `search_canvas_effects` | Search canvas effects by keyword, category, or interactivity |
|
|
64
53
|
| `get_canvas_effect` | Get full JS source, mountCanvas runtime, and embed HTML |
|
|
65
54
|
|
|
55
|
+
### Motion Recipes (Animation Patterns)
|
|
56
|
+
|
|
57
|
+
| Tool | Description |
|
|
58
|
+
|------|-------------|
|
|
59
|
+
| `list_motion_recipes` | List all motion recipes grouped by family |
|
|
60
|
+
| `search_motion_recipes` | Search recipes by keyword, family, technology, or trigger |
|
|
61
|
+
| `get_motion_recipe` | Get full self-contained HTML for a motion recipe |
|
|
62
|
+
|
|
66
63
|
### Fonts (Semantic Recommendations)
|
|
67
64
|
|
|
68
65
|
| Tool | Description |
|
|
@@ -78,13 +75,13 @@ The important invariant is different: MCP should provide context, discovery, and
|
|
|
78
75
|
|
|
79
76
|
## Content
|
|
80
77
|
|
|
81
|
-
### CSS Snippets (
|
|
78
|
+
### CSS Snippets (144)
|
|
82
79
|
|
|
83
80
|
Effects that Tailwind v4 can't do natively across 12 categories: glass, animations, easing, scroll, decorative, interactions, text, lighting, depth, masks, surfaces, atmosphere.
|
|
84
81
|
|
|
85
|
-
### UI Patterns (
|
|
82
|
+
### UI Patterns (519+)
|
|
86
83
|
|
|
87
|
-
Page sections and content elements across 170+ families — hero, navbar, pricing, features, dashboard, e-commerce, AI, and more. All using `--ws-*` component tokens.
|
|
84
|
+
Page sections and content elements across 170+ families — hero, navbar, pricing, features, dashboard, e-commerce, AI, developer tools, and more. All using `--ws-*` component tokens.
|
|
88
85
|
|
|
89
86
|
### Canvas Effects (3)
|
|
90
87
|
|
|
@@ -94,10 +91,25 @@ Dynamic JavaScript visuals using the `mountCanvas` runtime: particle fields, pro
|
|
|
94
91
|
|
|
95
92
|
Complete standalone pages: SaaS, agency, portfolio, shop, company — with Tailwind CDN.
|
|
96
93
|
|
|
94
|
+
### Motion Recipes (3)
|
|
95
|
+
|
|
96
|
+
Framework-agnostic animation patterns using GSAP and Motion One. Self-contained HTML files with live scroll demos. Families: reveal, scroll, transition, micro, layout.
|
|
97
|
+
|
|
97
98
|
### Font Recommendations (25 fonts, 15 pairings)
|
|
98
99
|
|
|
99
100
|
Semantic font stack recommendations based on domain (legal, saas, agency...) and tone (serious, modern, friendly...). All fonts available as npm packages via @fontsource.
|
|
100
101
|
|
|
102
|
+
## Offline Support
|
|
103
|
+
|
|
104
|
+
The MCP works without a permanent internet connection. Registry data is loaded using a layered fallback:
|
|
105
|
+
|
|
106
|
+
1. **In-memory cache** (5-min TTL) — no re-fetch within the same session
|
|
107
|
+
2. **Remote fetch** from webspire.de — always current, writes to disk when newer
|
|
108
|
+
3. **Disk cache** (`~/.cache/webspire/`) — last successfully fetched version, survives restarts
|
|
109
|
+
4. **Installed copy** — frozen at publish time, last resort
|
|
110
|
+
|
|
111
|
+
In practice: go online once, the disk cache is written. All subsequent offline starts use that cached version, not the potentially older installed copy.
|
|
112
|
+
|
|
101
113
|
## 3-Layer Token Architecture
|
|
102
114
|
|
|
103
115
|
```
|
|
@@ -151,4 +163,14 @@ const results = searchSnippets(registry, {
|
|
|
151
163
|
});
|
|
152
164
|
```
|
|
153
165
|
|
|
166
|
+
## Stability Model
|
|
167
|
+
|
|
168
|
+
Webspire is intentionally iterative.
|
|
169
|
+
|
|
170
|
+
- Registry contents, taxonomy, scoring, and composition output may change over time.
|
|
171
|
+
- The only guaranteed answer is the snapshot you receive when you make the request.
|
|
172
|
+
- This is by design: the registry keeps improving instead of acting like a fixed framework API.
|
|
173
|
+
|
|
174
|
+
The important invariant: MCP provides context, discovery, and composition help, while the resulting code remains something you own directly in your project. No runtime dependency is introduced.
|
|
175
|
+
|
|
154
176
|
Docs: https://webspire.de
|