MCP.so
登录

MCP 服务工具

@JQSC

基本信息

分类

其他

传输方式

stdio

作者

JQSC

关于 MCP 服务工具

mcp-server 合集

MCP 服务工具 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

MCP 服务工具 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is MCP 服务工具?

MCP 服务工具 is a Model Context Protocol server that provides tool integrations for AI service APIs. It currently supports Hugging Face (text, image, speech, zero‑shot tasks) and Dify (conversational and text generation apps) services. It is aimed at developers who want to use MCP to access these AI models through a unified interface.

How to use MCP 服务工具?

Install dependencies with npm install, create a .env file with the required API keys (HUGGINGFACE_API_KEY, DIFY_API_KEY, DIFY_BASE_URL), then start the Dify MCP service using npm run start:dify. For Hugging Face, import and call the tool functions directly in TypeScript, providing the API key and model parameters.

Key features of MCP 服务工具

  • Hugging Face: text generation, classification, QA, summarization, translation, fill‑mask
  • Hugging Face: image classification, segmentation, image‑to‑text, zero‑shot image/text classification
  • Hugging Face: automatic speech recognition
  • Dify: chat with conversation history support
  • Dify: text generation via completion endpoint
  • Dify: conversation listing and renaming

Use cases of MCP 服务工具

  • Build an MCP‑compliant chat interface that routes user messages to a Dify‑powered AI assistant.
  • Perform on‑the‑fly text or image classification using Hugging Face models without managing separate endpoints.
  • Integrate speech recognition into an MCP agent to transcribe audio blobs.
  • Generate summaries or translations of long documents through MCP tool calls.
  • Manage multiple Dify conversations (list, rename, fetch history) programmatically.

常见问题

1

What are the runtime dependencies?

Node.js (npm) is required. The README does not specify a minimum version, but `npm install` must succeed.

2

What API keys are needed?

For Hugging Face, set `HUGGINGFACE_API_KEY`. For Dify, set `DIFY_API_KEY` and `DIFY_BASE_URL`. These are added in a `.env` file in the project root.

3

Are there any usage limits or costs?

Yes. The README notes that users should be aware of API call limits and associated costs for both Hugging Face and Dify. Exact limits depend on the provider’s plan.

4

Does the server support authentication?

Authentication is handled via API keys supplied in the environment. There is no mention of other auth methods (e.g., OAuth).

5

What transport does MCP 服务工具 use?

The README does not specify the MCP transport (e.g., stdio, SSE). It only shows a start command (`npm run start:dify`) and TypeScript API usage.

评论

其他 分类下的更多 MCP 服务器