Skip to main content
Glama
deenesjakoruzh
torchv

TorchV AIS MCP Server

Official
by torchv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

@torchv-team/ais-mcp

English | 中文

License MCP

🚀 TorchV AIS 知识库 MCP 服务器

一个生产就绪的 MCP 服务器，支持直接对 AIS 企业知识库进行 读取 / 写入 / 编辑 / 文件传输 操作。

img.png

Related MCP server: Engineering Standards MCP Server

✨ 功能特性

  • 📚 统一访问 AIS 知识库

  • 🛠️ 完整的 MCP 工具链（读取 / 写入 / 管理）

  • ⚡ 通过 npx 一键启动

  • 🔌 同时支持 STDIO 和 HTTP (流式) 传输方式

  • 🔐 细粒度的权限控制 (readonly / write / admin)

🚀 安装与运行

npx -y @torchv-team/ais-mcp

🔑 必要配置

启动前，请设置以下环境变量：

export KB_EXECUTE_URL="https://bot.torchv.com"
export KB_TOKEN="your-token"

🌐 如何获取 KB_EXECUTE_URL

📌 步骤：

  1. 打开您的 AIS 实例

  2. 从浏览器地址栏复制站点源地址 (origin)

👉 示例：

https://bot.torchv.com

🔐 如何获取 KB_TOKEN

推荐：

AIS → Admin Center → API Keys → Create Key

临时（不推荐用于生产环境）：

Browser DevTools → Network → Inspect request → Copy token

⚙️ 可选配置

export KB_MODE="readonly"   # readonly | write | admin
export KB_TIMEOUT_SECONDS="30"
export KB_DEFAULT_REPO_CODE="TEAM_DOCS"
export KB_EXTRA_HEADERS_JSON='{"x-foo":"bar"}'

🛡️ 权限级别

  • 🟢 readonly → 只读访问

  • 🟡 write → 允许写入 / 上传 / 发布

  • 🔴 admin → 完全控制（移动 / 删除）

🧩 运行模式

🖥️ STDIO 模式（本地 MCP 客户端）

npm run build
node dist/cli.js

或：

npm run dev
npm run start

🌍 流式 HTTP 模式

npm run build
node dist/cli.js \
  --transport streamable-http \
  --host 127.0.0.1 \
  --port 3000 \
  --path /mcp

或：

npm run dev:http
npm run start:http

📌 参数：

--transport streamable-http
--host 127.0.0.1
--port 3000
--path /mcp

🔌 Claude / Codex 配置

STDIO

{
  "mcpServers": {
    "ais": {
      "command": "npx",
      "args": ["-y", "@torchv-team/ais-mcp"],
      "env": {
        "KB_EXECUTE_URL": "https://your-ais-domain",
        "KB_TOKEN": "your-token",
        "KB_MODE": "readonly"
      }
    }
  }
}

HTTP 模式

{
  "mcpServers": {
    "ais-http": {
      "type": "streamable-http",
      "url": "http://127.0.0.1:3000/mcp"
    }
  }
}

🛠️ 工具概览

📖 只读

  • kb_list_repos

  • kb_list_path

  • kb_tree

  • kb_search

  • kb_read_document

  • kb_render_link

  • kb_download_file

  • kb_get_download_link

✏️ 写入

  • kb_write_document

  • kb_patch_document

  • kb_create_directory

  • kb_copy_document

  • kb_publish_document

  • kb_upload_file

🔧 管理

  • kb_move_document

  • kb_delete_document

🧠 关于 AIS

AIS 是 TorchV 的核心产品——它不仅仅是一个传统的知识库，更是：

🧠 企业级 AI 知识引擎

核心能力

  • 🔄 将零散数据转化为结构化知识

  • 🔍 可搜索

  • 🧩 可治理

  • ⚡ 可组合

  • 📈 可优化

🎁 试用 AIS

📲 联系我们（CEO 微信）：

img.png

Available Tools

8 tools
kb_download_fileD
ParametersJSON Schema
NameRequiredDescriptionDefault
codeYes
localPathYes
extractIsNo
overwriteNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kb_list_pathD
ParametersJSON Schema
NameRequiredDescriptionDefault
pathYes
sortNo
limitNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kb_list_reposD
ParametersJSON Schema
NameRequiredDescriptionDefault
sortNo
limitNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kb_read_documentD
ParametersJSON Schema
NameRequiredDescriptionDefault
codeNo
nameNo
rangeNo
headNo
tailNo
lineNumbersNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kb_treeD
ParametersJSON Schema
NameRequiredDescriptionDefault
pathYes
depthNo
limitNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 8 tool updatesv0.1.4
    • First observedkb_download_file
    • First observedkb_get_download_link
    • First observedkb_list_path
    • First observedkb_list_repos
    • First observedkb_read_document
    • First observedkb_render_link
    • First observedkb_search
    • First observedkb_tree
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored across 8 tools

Disambiguation2/5

The tools have overlapping purposes that could cause confusion, particularly around file/document operations. For example, kb_download_file, kb_get_download_link, and kb_render_link all seem related to accessing files, but their specific distinctions are unclear without descriptions. Similarly, kb_list_path and kb_tree both appear to involve directory/file listing, creating ambiguity in tool selection.

Naming Consistency5/5

All tool names follow a perfectly consistent pattern: they all start with 'kb_' prefix and use snake_case throughout. This uniformity makes the tool set predictable and easy to parse, with no deviations in naming conventions across the eight tools.

Tool Count4/5

With 8 tools, the count is reasonable for a knowledge base or document management server. It's slightly on the higher side but still well-scoped, suggesting a focused domain without being overly sparse or bloated. The number aligns well with typical MCP server tool counts.

Completeness3/5

Inferring from tool names, the server seems designed for knowledge base operations (e.g., listing, reading, searching, downloading). However, there are notable gaps: there are no clear tools for creating, updating, or deleting content, which limits full CRUD coverage. The surface covers retrieval and listing well but misses modification capabilities, potentially causing agent workarounds.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers