Pinme Deploy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINME_API_KEY | No | Pinme API key (if using API deployment) |
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 |
|---|---|
| deploy_to_pinmeA | 将静态网站、HTML 文件或前端项目上传到 Pinme (IPFS)。支持单个文件或整个目录。如果未指定路径，会自动检测常见的构建输出目录（build、dist、out、.next 等）。 |
| check_pinme_statusB | 检查 Pinme 部署状态。可以通过 CID 或 ENS URL 检查。 |
| list_deploymentsB | 列出所有已部署的项目。 |
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 3 tools
Each tool has a clearly distinct purpose: check_pinme_status monitors deployment status, deploy_to_pinme handles uploading content, and list_deployments retrieves deployment history. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (check_pinme_status, deploy_to_pinme, list_deployments), using snake_case throughout. This predictability enhances usability and reduces cognitive load for agents.
With 3 tools, the server is well-scoped for deployment management, covering core operations like checking, uploading, and listing. It is slightly lean but reasonable, as additional tools (e.g., for deletion or updates) might be unnecessary for a simple deployment service.
The toolset covers essential deployment workflows: uploading, status checking, and listing. A minor gap exists in lacking a delete or update tool, but agents can work around this by re-deploying or managing deployments externally. The surface is largely complete for the stated purpose.