Skip to main content
Glama
Lingzhhiiii

Shoplazza MCP Tool

by Lingzhhiiii
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

Shoplazza MCP 工具

这是一个用于Cursor的MCP (Model Context Protocol) 工具，可以获取Shoplazza LessJS组件的文档信息。

功能

  • 获取LessJS组件的完整文档

  • 提取组件的属性、方法、事件和示例代码

  • 提供结构化的JSON格式输出

Related MCP server: Zendesign MCP Server

安装和配置

1. 构建项目

npm install
npm run build

2. 在Cursor中配置MCP

在Cursor中，你需要配置MCP服务器。有两种方式：

方式一：通过Cursor设置界面

  1. 打开Cursor

  2. 进入设置 (Settings)

  3. 搜索 "MCP" 或 "Model Context Protocol"

  4. 添加新的MCP服务器配置：

{
  "command": "node",
  "args": ["/path/to/your/shoplazza-mcp/build/index.js"],
  "env": {}
}

方式二：通过配置文件

在你的Cursor配置目录中创建或编辑MCP配置文件：

macOS: ~/Library/Application Support/Cursor/User/globalStorage/mcp-config.json Windows: %APPDATA%\Cursor\User\globalStorage\mcp-config.json Linux: ~/.config/Cursor/User/globalStorage/mcp-config.json

{
  "mcpServers": {
    "shoplazza-mcp": {
      "command": "node",
      "args": ["/path/to/your/shoplazza-mcp/build/index.js"],
      "env": {}
    }
  }
}

3. 重启Cursor

配置完成后，重启Cursor以使MCP工具生效。

使用方法

配置完成后，你可以在Cursor的对话中直接使用以下工具：

get-lessjs

获取LessJS组件的文档信息。

参数:

  • componentName (string): LessJS组件名称

使用示例:

请帮我获取spz-accordion组件的文档信息

返回数据:

  • 组件名称和描述

  • 使用场景

  • 属性列表（名称、类型、默认值、是否必需）

  • 方法列表（名称、参数）

  • 事件列表

  • 代码示例

支持的组件

目前支持所有在 https://lessjs.shoplazza.com/latest/components/ 上可用的组件，包括但不限于：

故障排除

  1. 工具未响应: 确保路径正确且文件存在

  2. 权限错误: 确保build/index.js有执行权限

  3. 网络错误: 检查网络连接和API地址是否可访问

开发

项目结构

shoplazza-mcp/
├── src/
│   ├── index.ts          # MCP服务器主文件
│   └── extractor.ts      # HTML解析和数据提取
├── build/                # 编译后的文件
├── package.json
└── README.md

添加新功能

  1. 在 src/index.ts 中添加新的工具定义

  2. 在 src/extractor.ts 中添加相应的数据提取逻辑

  3. 重新构建项目：npm run build

  4. 重启Cursor

Available Tools

1 tool
get-lessjsD
ParametersJSON Schema
NameRequiredDescriptionDefault
componentNameYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool stands alone with no other tools to confuse it with.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The naming pattern cannot be inconsistent when only one exists.

Tool Count2/5

One tool is too few for a server named 'Shoplazza MCP Tool', which suggests an e-commerce or store management domain. A single tool cannot provide meaningful coverage for such a broad purpose, making it severely under-scoped.

Completeness1/5

The server is severely incomplete for its implied e-commerce domain. With only a 'get-lessjs' tool (which lacks a description but seems unrelated to core store operations), there are no tools for managing products, orders, customers, or other essential store functions, leaving major gaps.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • DevEnvInfoServer

    carterlasalle
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that provides detailed information about your development environment to the Cursor code editor, enabling more context-aware assistance.
    7
    MIT

  • Zendesign MCP Server

    vishnumallela
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that allows Cursor users to fetch real-time information about Zendesign design system components.
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lingzhhiiii/shoplazza-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server