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 サーバー

AIS エンタープライズナレッジベースに対して直接 読み取り / 書き込み / 編集 / ファイル転送 操作を可能にする、本番環境対応の MCP サーバーです。

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. ブラウザのアドレスバーからサイトのオリジンをコピーする

👉 例：

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 WeChat）：

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