Teckel Ipfs Mcp Toolkit
About
The Interplanetary File System (IPFS) MCP toolkit gives AI Agents and automated workflows the ability to utilize IPFS as a backend storage medium. Upload, retrieve, pin, and manage encrypted files on IPFS via a simple API accessible as MCP tools.
Details
- Author
- teckel-mcp-servers
- Downloads
- 283
- Categories
- File Management, Other, Security, Developer Tools
Jump to
- List IPFS files with fuzzy nickname search and filters
- Upload files (raw or base64-encoded) to IPFS
- Retrieve IPFS content by CID
- Pin and unpin files on the teckel IPFS node
- Remove files from teckel node and account inventory
- Encryption of content using the API key (not end-to-end)
- Content pre‑scanned for malware and inappropriate material
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Teckel Ipfs Mcp ToolkitCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
First, download the teckel App from the App Store or Google Play and create an account. Generate an API key in the app’s Account settings. Then configure your MCP client (e.g., Cursor) with the server URL https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp and an Authorization header set to Bearer YOUR_API_KEY. Optionally, use ipfs-sse for legacy SSE protocol. Clients send natural language prompts which the server maps to IPFS tool calls.
list_ipfs_files
Get Ipfs Content For Wallet List IPFS files (selected on nickname via fuzzy search_string) for the account corresponding to the teckel API key used in the call ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
remove_ipfs_files
Remove Ipfs Files From Account 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. Note: this only removes the content from the teckel node and inventory. It may still exist on the IPFS de-centralized network. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
pin_ipfs_files
Pin Ipfs Files For Apikey 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. Pinning prevents automatic deletion of the content from the IPFS node. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
unpin_ipfs_files
Unpin Ipfs Files For Apikey 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. Unpinning allows automatic deletion of the content from the IPFS node. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
pin_ipfs_cid
Pin Ipfs Cid For Apikey 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. Pinning prevents automatic deletion of the content from the IPFS node. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
remove_ipfs_cid_from_account
Remove Ipfs Cid From Account 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. Note: this only removes the content from the teckel node and inventory. It may still exist on the IPFS de-centralized network. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
publish_ipfs_file_to_webserver
Publish Ipfs File To Webserver 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. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
upload_file_to_ipfs
Upload Sender File To Ipfs For Apikey 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. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
upload_base64_file_to_ipfs
Upload Sender Base64 To Ipfs For Apikey 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. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
retrieve_ipfs_file
Retrieve Ipfs File For Apikey Retrieve the contents of the IPFS file identified by the provided cid, from the inventory of the account corresponding to the teckel API key used in the call. Will automatically decrypt if encrypted. Only files originally posted to IPFS via teckel are supported i.e., not generic (non-teckel origin) IPFS content. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"teckel ipfs mcp toolkit": {
"teckel-ipfs-toolkit": {
"url": "https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp",
"headers": {
"Authorization": "Bearer <MY TECKEL APIKEY"
}
}
}
}
}McpServers
{
"teckel-ipfs-toolkit": {
"url": "https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp",
"headers": {
"Authorization": "Bearer <MY TECKEL APIKEY"
}
}
}ipfs-toolkit
Interplanetary File System (IPFS) MCP toolkitHow to Use the teckel Toolkits
First download and install the teckel App.
Next generate an API key using the teckel App.
Do the following:
1. 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.
2. 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.
3. For illustrative purposes, we will use the following fake key d1e12345-c234-45a6-9b76-1234567891ff in the examples presented below. You would substitute your actual API key in place of this fake key.
Next, decide if you are using the MCP servers or RESTful (API) to access the tools.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
