MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Store, retrieve, and pin encrypted files on IPFS via MCP tools for AI agents and workflows
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 11/100 | 热度 0 · 新鲜度 3 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-05-06 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 3/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Ipfs Toolkit。按照 https://mcp.popnx.com/i/tkllabs-bh-mcp-servers-ipfs-toolkit.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/4 项检查 · 你的提问会经过开发者的服务器(mcp-servers.bh.tkllabs.io) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Ipfs Toolkit 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Ipfs Toolkithttps://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsIpfs Toolkit
用 Ipfs Toolkit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Ipfs Toolkit,或回答中出现 Ipfs Toolkit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Ipfs Toolkit
Ipfs Toolkit 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Ipfs Toolkit 的应用
可连接 Claude Code · 约 5 分钟
需要 Ipfs Toolkit 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user ipfs-toolkit https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Ipfs Toolkit 在列表中并显示已连接
用 Ipfs Toolkit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Ipfs Toolkit,或回答中出现 Ipfs Toolkit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Ipfs Toolkit 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Ipfs Toolkit 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ipfs Toolkit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Ipfs Toolkit,或回答中出现 Ipfs Toolkit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Ipfs Toolkit 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Ipfs Toolkit 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ipfs Toolkit 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Ipfs Toolkit,或回答中出现 Ipfs Toolkit 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user ipfs-toolkit https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ipfs-toolkit": {
"url": "https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"ipfs-toolkit": {
"type": "http",
"url": "https://mcp-servers.bh.tkllabs.io:9780/ipfs-mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过域名 mcp-servers.bh.tkllabs.io 验证(注册中心会核实域名所有权)
代码最后更新于6个月前,已超过 6 个月
不适用:由 mcp-servers.bh.tkllabs.io 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 52 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/tkllabs-bh-mcp-servers-ipfs-toolkit)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于6个月前,最新版本(1.0.1)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 Ipfs Toolkit | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 是 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/4 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | – | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Interplanetary File System (IPFS) MCP toolkit
Do the following:
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).
{
"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”.
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 (via _teckel credits_ purchased within the teckel App) for usage of teckel IPFS services can be found at https://teckel.io/pricing/
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.
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).
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.
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.
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.
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.
Base URL: https://mcp-servers.bh.tkllabs.io:9780
All endpoints require a Bearer token in the Authorization header:
Authorization: Bearer YOUR_API_KEY
| 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 |
/get_ipfs_content_for_apikeyList 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"
/remove_ipfs_files_from_accountUnpin 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"
/pin_ipfs_files_for_apikeyPin 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"
/unpin_ipfs_files_for_apikeyUnpin 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.