Ipfs Toolkit
This connects Claude to IPFS through the teckel platform's hosted endpoints. You get tools to upload files (raw or base64), retrieve content by CID, manage pinning, and optionally encrypt uploads using your teckel API key as the encryption basis. The server exposes about ten operations including fuzzy search over your uploaded files by nickname, batch pin/unpin actions, and publishing files to teckel's web server. You'll need the teckel mobile app to generate an API key tied to an Ethereum account, then configure your MCP client with Bearer token auth. Calls are metered through teckel credits with rate limiting per key. Worth noting that teckel-based encryption isn't end-to-end since the service knows your key, so pre-encrypt sensitive files offline before upload if that matters for your use case.
- tools
- 9
- auth
- Secret needed
- transport
- HTTP, SSE
- last updated
- May 6, 2026
Tools
9 toolsPublic tool metadata for what this MCP can expose to an agent.
list_ipfs_filesList IPFS files (selected on nickname via fuzzy search_string) for the account corresponding to the teckel API key used in the call.
List IPFS files (selected on nickname via fuzzy search_string) for the account corresponding to the teckel API key used in the call.
No parameter schema in public metadata yet.
remove_ipfs_filesUnpin and remove the IPFS files (selected on nickname via fuzzy search_string) from the teckel IPFS node and from the wallet account, for the account corresponding to the teckel API key used in the call.
Unpin and remove the IPFS files (selected on nickname via fuzzy search_string) from the teckel IPFS node and from the wallet account, for the account corresponding to the teckel API key used in the call.
No parameter schema in public metadata yet.
pin_ipfs_filesPin the IPFS files (selected on nickname via fuzzy search_string) on to the teckel IPFS node for the account corresponding to the teckel API key used in the call.
Pin the IPFS files (selected on nickname via fuzzy search_string) on to the teckel IPFS node for the account corresponding to the teckel API key used in the call.
No parameter schema in public metadata yet.
unpin_ipfs_filesUnpin the IPFS files (selected on nickname via fuzzy search_string) from the teckel IPFS node for the account corresponding to the teckel API key used in the call.
Unpin the IPFS files (selected on nickname via fuzzy search_string) from the teckel IPFS node for the account corresponding to the teckel API key used in the call.
No parameter schema in public metadata yet.
pin_ipfs_cidPin the individual entity identified by its IPFS CID on to the teckel IPFS node for the account corresponding to the teckel API key used in the call.
Pin the individual entity identified by its IPFS CID on to the teckel IPFS node for the account corresponding to the teckel API key used in the call.
No parameter schema in public metadata yet.
remove_ipfs_cid_from_accountUnpin and remove the individual entity identified by its IPFS CID from the teckel IPFS node and from the wallet account, for the account corresponding to the teckel API key used in the call.
Unpin and remove the individual entity identified by its IPFS CID from the teckel IPFS node and from the wallet account, for the account corresponding to the teckel API key used in the call.
No parameter schema in public metadata yet.
publish_ipfs_file_to_webserverRetrieve the IPFS file, identified by its IPFS CID, from the teckel IPFS node, and publish it on the teckel web server, applying decryption if necessary, for the account corresponding to the teckel API key used in the call, returning the browseable URL.
Retrieve the IPFS file, identified by its IPFS CID, from the teckel IPFS node, and publish it on the teckel web server, applying decryption if necessary, for the account corresponding to the teckel API key used in the call, returning the browseable URL.
No parameter schema in public metadata yet.
upload_file_to_ipfsUpload file contents to the teckel IPFS node for the account corresponding to the teckel API key used in the call. The content will be pre-scanned for compatibility with the teckel terms and will be rejected if not compliant.
Upload file contents to the teckel IPFS node for the account corresponding to the teckel API key used in the call. The content will be pre-scanned for compatibility with the teckel terms and will be rejected if not compliant.
No parameter schema in public metadata yet.
upload_base64_file_to_ipfsUpload base64-encoded file contents to the teckel IPFS node for the account corresponding to the teckel API key used in the call. The content will be pre-scanned for compatibility with the teckel terms and will be rejected if not compliant.
Upload base64-encoded file contents to the teckel IPFS node for the account corresponding to the teckel API key used in the call. The content will be pre-scanned for compatibility with the teckel terms and will be rejected if not compliant.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
ipfs-toolkit
Interplanetary File System (IPFS) MCP toolkit
How to Use the teckel Toolkits
First, download and install the teckel App.
Next, generate an API key using the teckel App.
Do the following:
-
Navigate to the Accounts page by tapping on the wallet icon in the upper right corner of the App home screen. Access the API Key Manager for the created or imported Ethereum Account by tapping “Manage API Key” on the Accounts page.
-
Use the API key when making calls to the endpoints. All the available endpoints are available via the teckel App, incorporating the actual API key for the given Ethereum Account.
Details
- Repository
- github.com/teckel-mcp-servers/ipfs-toolkit
- Transport
- HTTP, SSE
- Auth
- Required
- Registry
- MCP registry, active