mcp-ipfs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| W3_LOGIN_EMAIL | Yes | The email address used for w3 login, must be the same as the one used for 'w3 login' |
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 |
|---|---|
| w3_account_lsA | Lists all accounts the current agent is authorized for. Use this command after |
| w3_bridge_generate_tokensC | Generates authentication tokens for using the UCAN-HTTP bridge. |
| w3_can_access_claimC | Claims delegated capabilities for the authorized account using a provided proof. |
| w3_can_blob_addC | Stores a single file as a blob directly with the service. Requires ABSOLUTE paths for file arguments. |
| w3_can_blob_lsB | Lists blobs stored in the current space. |
| w3_can_blob_rmC | Removes a blob from the store by its base58btc encoded multihash. |
| w3_can_filecoin_infoC | Gets Filecoin deal information for a given Piece CID (advanced use). |
| w3_can_index_addC | Registers an index CID with the service (advanced use). Please refer to storacha.network documentation for details on indices. |
| w3_can_store_addA | Stores a CAR file with the service (advanced use). This is often a prerequisite for |
| w3_can_store_lsC | Lists stored CAR files (shards) in the current space (advanced use). |
| w3_can_store_rmA | Removes a stored CAR shard by its CID (advanced use). Use with extreme caution, as this deletes the underlying data shard. |
| w3_can_upload_addA | Manually registers an upload DAG by its root CID and shard CIDs (advanced use). This is typically used after storing CAR shards manually. |
| w3_can_upload_lsC | Lists uploads registered in the current space (advanced view, shows underlying structure). |
| w3_can_upload_rmA | Removes an upload listing by its root CID (advanced use). Does not remove the underlying blobs/shards. |
| w3_coupon_createC | Attempts to create/claim a coupon using a claim code. |
| w3_delegation_createC | Tool for w3_delegation_create operation. Requires ABSOLUTE paths for file arguments. |
| w3_delegation_lsD | Tool for w3_delegation_ls operation. |
| w3_delegation_revokeC | Tool for w3_delegation_revoke operation. Requires ABSOLUTE paths for file arguments. |
| w3_key_createA | Generates and prints a new ed25519 key pair. Does not automatically use it for the agent. |
| w3_loginA | Initiates the w3 login process using the pre-configured email (W3_LOGIN_EMAIL env var). IMPORTANT: The command expects email confirmation, so before running the |
| w3_lsD | Tool for w3_ls operation. |
| w3_openD | Tool for w3_open operation. |
| w3_plan_getB | Displays the plan associated with the current or specified account. |
| w3_proof_addC | Tool for w3_proof_add operation. Requires ABSOLUTE paths for file arguments. |
| w3_proof_lsC | Tool for w3_proof_ls operation. |
| w3_resetA | DANGEROUS: Resets the agent state, removing all proofs and delegations but retaining the agent DID. Requires explicit confirmation argument. |
| w3_rmC | Tool for w3_rm operation. |
| w3_space_addD | Tool for w3_space_add operation. |
| w3_space_createA | Creates a new space with a user-friendly name. NOTE: |
| w3_space_infoC | Tool for w3_space_info operation. NOTE: |
| w3_space_lsC | Tool for w3_space_ls operation. NOTE: |
| w3_space_provisionB | Associates a space with a customer/billing account. |
| w3_space_useD | Tool for w3_space_use operation. |
| w3_upC | Generates and prints a new ed25519 key pair. Does not automatically use it for the agent. Requires ABSOLUTE paths for file arguments. |
| w3_usage_reportB | Displays a storage usage report for the current or specified space. |
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 35 tools
The tools have overlapping purposes that could cause confusion, such as w3_can_blob_add and w3_can_store_add both handling file storage with similar requirements, and w3_key_create and w3_up both generating key pairs. However, descriptions provide some clarity, and many tools target distinct resources like accounts, spaces, and uploads, reducing ambiguity.
Most tools follow a consistent w3_ prefix with snake_case and verb_noun patterns like w3_account_ls, w3_space_create, and w3_can_blob_add. Minor deviations exist, such as w3_up being less descriptive and some tools having vague names like w3_ls or w3_open, but overall naming is predictable and readable.
With 35 tools, the count is excessive for the apparent scope of IPFS and account management, making it heavy and potentially overwhelming. A more focused set of 10-20 tools would be more appropriate, as many tools like w3_can_index_add and w3_can_upload_rm are marked as advanced use, suggesting unnecessary complexity.
The toolset provides comprehensive coverage for IPFS operations, including account management, file storage, space handling, and advanced features like CAR file management. Minor gaps exist, such as limited error handling tools or missing interactive commands like w3_space_create, but core workflows are well-supported with CRUD-like operations for blobs, stores, and uploads.