Teckel Ipfs Mcp Toolkit

MCP开发工具

提供方 teckel-mcp-servers

开发工具 HTTP · 远程 API Key 社区 / 第三方 CursorCodexZed
查看接入方式

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.

一句话选型结论

按资料字段整理

Teckel Ipfs Mcp Toolkit 属于开发工具类 MCP 服务器,HTTP · 远程,API Key,可直接接入 Cursor、Codex、Zed,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权API Key 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

encryption ipfs decentralized storage n8n voice agent

支持客户端

适用场景

encryptionipfsdecentralized storage

安装与配置

HTTP · 远程 API Key
连远程 HTTPS 端点,通常为 Streamable HTTP
https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp

把它填进客户端的 MCP 配置即可,不需要在本地安装运行时。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Teckel Ipfs Mcp Toolkit当前 未标注 HTTP · 远程 远程部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方teckel-mcp-servers上游标注的维护方 teckel-mcp-servers
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

17.5 KB
来自项目仓库与上游目录的原文,未做删改

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:

  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.

Using the MCP Servers

Configure your MCP client-of-choice

Whatever the client, the configuration is essentially the same. Namely, provide the client with the MCP server endpoint and access credentials. These are typically in the form of a configuration JSON snippet, using your API key as the “Bearer” token in the “Authorization” tag. For example, here is the precise configuration for use with the Cursor desktop app (navigate within the Cursor app to the Cursor Settings -> Tools & MCP -> + New MCP server and enter these details using your actual teckel API key to replace this fake one).

MCP JSON configuration (example for use with Cursor)```

{
"mcpServers": {
"teckel-ipfs-toolkit": {
"url": "https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp",
"headers": {
"Authorization": "Bearer d1e12345-c234-45a6-9b76-1234567891ff"
}
}
}
}

NOTE: This configuration assumes the HTTP(streamable) protocol. If your client requires the older (now legacy) SSE protocol, replace “ipfs-mcp” with “ipfs-sse”.

# Using the RESTful API Servers
The benefit of using the MCP servers is that the connected LLMs can parse the natural language in the user prompts, populate the required parameters for calling the toolbox API functions, then likewise unravel the returned JSON structure into natural language for presentation to the user. However, if you wish to utilise the teckel toolkits at a lower level (e.g., in your own app), you can call the functions directly using the RESTful (POST) API protocols. You are then responsible for populating the input parameters, and handling the returned JSON output. All methods called via RESTful web services must be "awaited": there is no fire-and-forget (with future polling for task completion etc).

## Pricing
Pricing (via _teckel credits_ purchased within the teckel App) for usage of teckel IPFS services can be found at https://teckel.io/pricing/

## Rate Limiting
All MCP/API calls are subject to rate-limiting per API key. The thresholds are not published, but if a given API key has exceeded the rate limit, a 429 error code will be returned on the given call.

## Errors
If the MCP/API call fails due to user error resulting in a 4xx error code, the user is charged one Base Call Fee (see https://teckel.io/ai-mcp-services/). If the API call fails due to server error resulting in a 5xx error code, the user is not charged. If the given call is part of a cascade of nested calls, the above rules apply to the “outer” call: In other words, if the outer call fails with a 4xx error code, the user is charged one Base Call Fee (for the failed outer call), and there will be no charge for any of the cascaded calls (whether they succeeded or not). Likewise, if the outer call fails with a 5xx error code, the user is not charged at all (even if the cascaded calls succeed).

## Encryption
IPFS is a public service and all content is in principle available to anyone. Therefore if you deem your content to be private, you should make sure it is encrypted before uploading to IPFS. Teckel facilitates such encryption using your teckel API key to construct the encryption key. However, this does not provide end-to-end encryption of your content because your API key is known to the teckel servers. Instead, if you require end-to-end encryption, whereby only you (and not the teckel servers etc) can ever retrieve your content, you must first encrypt your files offline using your own chosen method, before uploading to IPFS via teckel.

## Content moderation
To play our part in keeping the internet clean, teckel pre-scans all uploaded content for malware and inappropriate content (as per the teckel terms). Any content failing the pre-scan is rejected. The ethereum wallet address associated with the API key used for the attempted upload may be blacklisted at teckel's sole discretion.

## API Key Security
Should you have concerns that your API key has been compromised (and someone else may be consuming your teckel credits by using your key), simply replace the key via the API Key Manager → Replace API key in the teckel App. The old key will then be immediately disabled. IMPORTANT: if you change your API key, any IPFS content previously encrypted via teckel will no longer be retrievable since the API key is used for encryption. Before you change your API key, make sure you have retrieved (and unencrypted) your previous IPFS data and stored the unencrypted versions offline.

## teckel App
The IPFS toolkit functionality is wholly compatible with the IPFS functionality of the teckel app. This means that IPFS content uploaded via the teckel App can be accessed via the IPFS toolkit, and vice versa.

# teckel MCP Server — IPFS API Reference

**Base URL:** `https://mcp-servers.bh.tkllabs.io:9780`

---

## Authentication

All endpoints require a Bearer token in the `Authorization` header:```
Authorization: Bearer YOUR_API_KEY

Endpoint Index

Method Path MCP Tool Name Description
POST /get_ipfs_content_for_apikey list_ipfs_files List IPFS files for account
POST /remove_ipfs_files_from_account remove_ipfs_files Remove multiple IPFS files by nickname search
POST /pin_ipfs_files_for_apikey pin_ipfs_files Pin multiple IPFS files by nickname search
POST /unpin_ipfs_files_for_apikey unpin_ipfs_files Unpin multiple IPFS files by nickname search
POST /pin_ipfs_cid_for_apikey pin_ipfs_cid Pin a single IPFS file by CID
POST /remove_ipfs_cid_from_account remove_ipfs_cid_from_account Remove a single IPFS file by CID
POST /publish_ipfs_file_to_webserver publish_ipfs_file_to_webserver Publish an IPFS file to the teckel web server
POST /upload_sender_file_to_ipfs_for_apikey upload_file_to_ipfs Upload a file to IPFS
POST /upload_sender_base64_to_ipfs_for_apikey upload_base64_file_to_ipfs Upload base64-encoded file to IPFS
POST /retrieve_ipfs_file_for_apikey retrieve_ipfs_file Retrieve an IPFS file by CID

Endpoints


POST /get_ipfs_content_for_apikey

List IPFS files for the account associated with the API key, with optional filtering by nickname, pinned status, encrypted state, and content type.

MCP tool: list_ipfs_files — List IPFS files (selected on nickname via fuzzy search_string) for the account corresponding to the teckel API key used in the call.

Parameters

Name Type Required Default Description
search_string string No "" Search for this string in the file nickname. Leave blank to return all.
pinned_state integer No 0 0 = all entries; 1 = pinned only; 2 = unpinned only
encrypted_state integer No 0 0 = all entries; 1 = encrypted only; 2 = unencrypted only
content_type string No "" Filter by content type, e.g. image, audio, video. Leave blank to ignore.
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/get_ipfs_content_for_apikey?search_string=my_video&pinned_state=0&encrypted_state=0&content_type=video" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /remove_ipfs_files_from_account

Unpin and remove IPFS files (selected by fuzzy nickname search) from the teckel IPFS node and account inventory.

> Note: This only removes content from the teckel node and inventory. The content may still exist on the decentralised IPFS network.

MCP tool: remove_ipfs_files — 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 decentralised network.

Parameters

Name Type Required Default Description
search_string string No "" Search for this string in the file nickname. Leave blank to match all.
pinned_state integer No 0 0 = all entries; 1 = pinned only; 2 = unpinned only
encrypted_state integer No 0 0 = all entries; 1 = encrypted only; 2 = unencrypted only
content_type string No "" Filter by content type, e.g. image, audio, video. Leave blank to ignore.
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/remove_ipfs_files_from_account?search_string=old_test_files&pinned_state=0&encrypted_state=0" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /pin_ipfs_files_for_apikey

Pin IPFS files (selected by fuzzy nickname search) on the teckel IPFS node. Pinning prevents automatic garbage collection of the content.

MCP tool: pin_ipfs_files — 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.

Parameters

Name Type Required Default Description
search_string string No "" Search for this string in the file nickname. Leave blank to match all.
pinned_state integer No 0 0 = all entries; 1 = pinned only; 2 = unpinned only
encrypted_state integer No 0 0 = all entries; 1 = encrypted only; 2 = unencrypted only
content_type string No "" Filter by content type, e.g. image, audio, video. Leave blank to ignore.
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/pin_ipfs_files_for_apikey?search_string=important_files&pinned_state=2" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /unpin_ipfs_files_for_apikey

Unpin IPFS files (selected by fuzzy nickname search) from the teckel IPFS node. Unpinned files are eligible for automatic garbage collection.

MCP tool: unpin_ipfs_files — 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.

Parameters

Name Type Required Default Description
search_string string No "" Search for this string in the file nickname. Leave blank to match all.
pinned_state integer No 0 0 = all entries; 1 = pinned only; 2 = unpinned only
encrypted_state integer No 0 0 = all entries; 1 = encrypted only; 2 = unencrypted only
content_type string No "" Filter by content type, e.g. image, audio, video. Leave blank to ignore.
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/unpin_ipfs_files_for_apikey?search_string=old_drafts&pinned_state=1" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /pin_ipfs_cid_for_apikey

Pin the individual IPFS entity identified by its CID on the teckel IPFS node. Pinning prevents automatic deletion.

MCP tool: pin_ipfs_cid — 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.

Parameters

Name Type Required Default Description
cid string No "" IPFS content identifier of the file to pin
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/pin_ipfs_cid_for_apikey?cid=QmExampleCID123" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /remove_ipfs_cid_from_account

Unpin and remove the individual IPFS entity identified by its CID from the teckel IPFS node and account inventory.

> Note: This only removes content from the teckel node and inventory. The content may still exist on the decentralised IPFS network.

MCP tool: 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 decentralised network.

Parameters

Name Type Required Default Description
cid string No "" IPFS content identifier of the file to remove
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/remove_ipfs_cid_from_account?cid=QmExampleCID123" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /publish_ipfs_file_to_webserver

Retrieve an IPFS file by CID from the teckel node and publish it on the teckel web server, applying decryption if necessary. Returns a browseable public URL.

MCP tool: 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.

Parameters

Name Type Required Default Description
cid string No "" IPFS content identifier of the file to publish
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/publish_ipfs_file_to_webserver?cid=QmExampleCID123" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /upload_sender_file_to_ipfs_for_apikey

Upload a file to the teckel IPFS node for the account associated with the API key. The content is pre-scanned for compliance with teckel terms before being accepted.

MCP tool: upload_file_to_ipfs — 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.

Parameters

Name In Type Required Default Description
file multipart form body file Yes — File to upload
nicknameOnIPFS query string No "" Nickname for the IPFS listing. Auto-generated if blank.
doEncryptOnIPFS query string No "false" Apply encryption before uploading. true or false.
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/upload_sender_file_to_ipfs_for_apikey?nicknameOnIPFS=my_document&doEncryptOnIPFS=false" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@/path/to/your/file.pdf"

POST /upload_sender_base64_to_ipfs_for_apikey

Upload base64-encoded file data to the teckel IPFS node for the account associated with the API key. The content is pre-scanned for compliance with teckel terms before being accepted.

MCP tool: upload_base64_file_to_ipfs — 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.

Parameters

Name Type Required Default Description
base64_data string No "" Base64-encoded file data
nicknameOnIPFS string No "" Nickname for the IPFS listing. Auto-generated if blank.
doEncryptOnIPFS string No "false" Apply encryption before uploading. true or false.
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/upload_sender_base64_to_ipfs_for_apikey?base64_data=SGVsbG8gV29ybGQ%3D&nicknameOnIPFS=my_file&doEncryptOnIPFS=false" \
  -H "Authorization: Bearer YOUR_API_KEY"

POST /retrieve_ipfs_file_for_apikey

Retrieve the contents of an IPFS file by CID from the account inventory. Automatically decrypts if the file is encrypted. Only files originally posted to IPFS via teckel are supported.

MCP tool: retrieve_ipfs_file — 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.

Parameters

Name Type Required Default Description
cid string No "" IPFS content identifier of the file to retrieve
curl -X POST "https://mcp-servers.bh.tkllabs.io:9780/retrieve_ipfs_file_for_apikey?cid=QmExampleCID123" \
  -H "Authorization: Bearer YOUR_API_KEY"

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Teckel Ipfs Mcp Toolkit 怎么安装?

在客户端按下面的安装命令接入:https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp。装完在客户端配置里引用同一个包或端点。

Teckel Ipfs Mcp Toolkit 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Teckel Ipfs Mcp Toolkit 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Teckel Ipfs Mcp Toolkit 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Teckel Ipfs Mcp Toolkit 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Teckel Ipfs Mcp Toolkit 能提供哪些能力?

资料显示能力标签包括 encryption、ipfs、decentralized storage、n8n、voice agent。具体工具清单以官方文档为准。

Teckel Ipfs Mcp Toolkit 需要什么运行环境?

运行时为 Cross-platform;属于远程端点,不需要在本地装运行时。

Teckel Ipfs Mcp Toolkit 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。