YAPI Interface MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yapi-get-interfaceC | 根据接口ID获取YAPI接口详情，支持格式：数字ID |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching YAPI interface details by ID.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'yapi-get-interface' follows a clear verb_noun pattern and is descriptive.
A single tool is too few for a server named 'YAPI Interface MCP Server', which implies a broader scope for managing YAPI interfaces. This minimal set severely limits functionality and suggests an incomplete implementation.
The tool set is severely incomplete for the domain of YAPI interface management. It only provides a 'get' operation, lacking essential CRUD operations like create, update, delete, or list interfaces, which are necessary for basic agent workflows.