Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Ai Doctor Api Ai Medical Chatbot Healthcare Ai Assistant MCP Server What are the common symptoms of a brain tumor?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Zydsoft MCP Server
这是一个 MCP 服务器，用于访问 Ai Doctor Api Ai Medical Chatbot Healthcare Ai Assistant API。
PyPI 包名: bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant
版本: 2.0.0
传输协议: stdio
pip install bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistantpip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant bach_ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant
# 或指定版本
uvx --from bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant@latest bach_ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistantpython server.py# 安装
pip install bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant
# 运行（命令名使用下划线）
bach_ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant": {
"command": "uvx",
"args": ["--from", "bach-ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant", "bach_ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}注意: 请将 E:\path\to\ai_doctor_api_ai_medical_chatbot_healthcare_ai_assistant\server.py 替换为实际的服务器文件路径。
此服务器提供以下工具:
neurosurgeryNeurosurgery
端点: POST /chat
参数:
noqueue (string): Example value: 1
传输协议: stdio
HTTP 客户端: httpx
此服务器由 API-to-MCP 工具自动生成。
版本: 2.0.0
Neurosurgery
| Name | Required | Description | Default |
|---|---|---|---|
| noqueue | No | Example value: 1 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description gives no behavioral information such as side effects, permissions required, or return behavior. The agent has no clue what the tool actually does.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single word that fails to convey any useful information. It is under-specified, not concise in a helpful way.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, output schema, and sibling tools, the description is completely inadequate. It provides no help for the agent to understand or use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'noqueue' has a description that just gives an example value, not clarifying its purpose. The tool description adds no meaning beyond the schema, which itself is uninformative.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is given. There is no indication of when to use this tool or which alternatives exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v2.0.0neurosurgeryScored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool 'neurosurgery' has a distinct purpose, even if vaguely described.
With a single tool, naming consistency is trivial. However, the name 'neurosurgery' is a noun rather than a verb_noun pattern, which is slightly atypical but not inconsistent.
The server name implies a broad healthcare AI assistant, but it offers only one tool. This is a severe mismatch; the tool count is far too low for the claimed domain.
The tool surface is severely incomplete. A healthcare AI assistant would need many more capabilities (e.g., general diagnosis, symptom checking, other specialties). Covering only neurosurgery leaves obvious gaps.
Your MedNode health vault in your AI assistant — records, summaries, labs, appointments.
Physician-reviewed medical opinions and prescriptions for AI agents.
Medical RAG: semantic search for clinical guidelines, drug interactions, diagnoses & EHR data.
Medical RAG: semantic search for clinical guidelines, drug interactions, diagnoses & EHR data.
