@efolusi/meridian-mcp 0.1.2 → 0.1.3

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.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/package.json +1 -1
  3. package/server.mjs +1 -1
package/README.md CHANGED
@@ -48,7 +48,7 @@ claude mcp add meridian -- npx -y @efolusi/meridian-mcp
48
48
  ```
49
49
 
50
50
  Then ask your agent things like *"list Meridian form components"*, *"show me the
51
- DatePicker props and usage"*, or *"build an Efolusi settings page with Meridian"* —
51
+ Calendar props and date-picker composition"*, or *"build an Efolusi settings page with Meridian"* —
52
52
  it will pull the real source and tokens before writing code.
53
53
 
54
54
  ## Run locally / develop
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@efolusi/meridian-mcp",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "MCP server exposing the Meridian design system registry (components, source, types, usage guides, tokens) to AI coding agents.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://meridian.efolusi.com",
package/server.mjs CHANGED
@@ -66,7 +66,7 @@ server.registerTool(
66
66
  {
67
67
  title: 'Get a Meridian component',
68
68
  description: "Full detail for one component by name: description, dependencies, and every file's real content — the .jsx source, the .d.ts types, and the .prompt.md usage guide. Use this before writing code that uses the component.",
69
- inputSchema: { name: z.string().describe('Component name, e.g. "Button", "DatePicker", "NumberInput".') },
69
+ inputSchema: { name: z.string().describe('Component name, e.g. "Button", "Calendar", "NumberInput".') },
70
70
  },
71
71
  async ({ name }) => {
72
72
  let c;