xiaobenyang-mcp-2-1
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@xiaobenyang-mcp-2-1 show me today's top headlines"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local Filesystem MCP Server
A Model Context Protocol (MCP) server for exploring local filesystems with glob and grep tools.
Built with Smithery SDK
Features
This server provides two essential tools for filesystem exploration:
glob - Find files matching patterns (e.g.,
**/*.ts,src/**/*.js)grep - Search for text patterns in files
Related MCP server: wangyue
Prerequisites
Smithery API key: Get yours at smithery.ai/account/api-keys
Getting Started
Install dependencies:
npm installStart development server:
npm run dev
The server will run locally and provide access to your filesystem through the MCP protocol.
Configuration
You can customize the working directory in your smithery.yaml config:
runtime: typescript
target: local
config:
workingDirectory: /path/to/your/directoryBy default, it uses the current working directory.
Development
Your code is organized as:
src/xiaobenyang_mcp_tools.ts.bak- MCP server with glob and grep toolssmithery.yaml- Runtime specification withtarget: localfor filesystem access
Edit src/xiaobenyang_mcp_tools.ts.bak to add your own filesystem tools.
Build
npm run buildCreates bundled server in .smithery/
Deploy
This server uses target: local in smithery.yaml, which means it's designed to run locally with filesystem access. It cannot be deployed to remote Smithery hosting.
Learn More
Available Tools
2 toolsget_all_dishesB
获取所有可用菜品的名称列表 (菜单)。
Inputs: no named parameters.
get_dish_contentC
根据提供的菜品名称获取其详细内容。
Inputs: dishName (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have perfectly distinct purposes: get_all_dishes retrieves a list of dish names, while get_dish_content fetches detailed content for a specific dish. There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is predictable and clear across the set.
With only 2 tools, this server feels thin for a dish/recipe domain. While the tools cover basic retrieval, typical food-related servers would include operations like search, filter, create, update, or delete dishes for a more complete surface.
The server only provides read operations (list and get details), lacking any create, update, delete, or search capabilities. This is a significant gap that will limit agent workflows, as there's no way to modify or interact with dish data beyond viewing it.
Related MCP Connectors
Image URL → plain text OCR for bots. Free try then prepaid TEST. https://ocr.kymac.co
Create online knowledge tests and quizzes, share a link, see results. Search ready-made tests.
Test the voice agents you run: scored transcripts, pass/fail verdicts, latency and WER metrics.
Related MCP Servers
- -
- -
- -
- -