SiliconFlow Image Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment mode (set to 'development' for detailed logs) | production |
| SILICONFLOW_API_KEY | Yes | SiliconFlow API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | 使用 SiliconFlow API 生成图片并保存到本地文件系统。 支持异步轮询获取图片，避免超时问题。 适用于博客封面、头像等各种场景的图片生成。 性能优化：
|
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 confusion between tools. The tool's purpose is clearly stated in its description, making it unambiguous.
The tool name 'generate_image' follows a standard verb_noun convention, which is clear and predictable. Even with a single tool, the naming is consistent and appropriate.
Having only one tool is too few for a server that might support a broader image generation workflow. The description hints at various use cases but provides no additional management or utility tools, making the tool set feel underdeveloped.
The single tool covers the primary task of generating and saving an image, which is the core functionality. However, there are no additional tools for listing, retrieving, or managing generated images, which could be considered minor gaps depending on the workflow.