MCP Development Framework
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_csvA | 解析CSV文件内容，支持各种编码格式 |
| parse_excelB | Parses an Excel file and returns its content including all sheets |
| parse_pdfB | 解析PDF文件内容，支持快速预览和完整解析两种模式 |
| parse_wordB | 解析Word文档内容，提取文本、表格和图片信息 |
| parse_markdownB | 解析Markdown文件内容，提取标题结构、列表和文本内容 |
| parse_fileC | 解析文件内容，支持PDF、Word、Excel、CSV和Markdown格式 |
| maxkbC | 请求MaxKB API并返回处理后的结果 |
| urlB | Fetches a website and returns its content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are mostly distinct: specific parsers for file types, but parse_file overlaps with all of them. maxkb and url are separate, causing some ambiguity.
Most tools follow 'parse_' prefix, but maxkb and url deviate. Naming is partially consistent but has outliers.
8 tools is a reasonable count, but the server name 'MCP Development Framework' suggests broader scope than just file parsing and URL fetching.
The toolkit covers file parsing well, but lacks other development operations (e.g., writing, API management). Gaps make it incomplete for a framework.