MEFS MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEFS_PRIVATE_KEY | Yes | Your EVM private key used for authentication and storage operations. | |
| MCP_TRANSPORT_MODE | No | Transport mode for MCP server. | stdio |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrieveA | Retrieve a file from MEFS storage by its CID (Content ID). Returns the file content as a base64 encoded string. |
| uploadA | Upload a file to MEFS storage. The file must be provided as a base64 encoded string. Returns the CID (Mid) of the uploaded file. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a file by CID, the other uploads a file. There is no overlap or ambiguity.
Both tool names are single lowercase verbs ('retrieve', 'upload') following a consistent pattern.
With only two tools, the server feels thin for a storage system, but it covers the core upload and retrieve operations. It is borderline but reasonable for a very focused use case.
Obvious gaps exist: there is no tool for listing stored files, deleting files, or updating existing content. These missing operations will cause agent failures if management beyond upload/retrieve is needed.