Skip to main content
Glama
TorchV AIS MCP Server

TorchV AIS MCP Server

Official
by torchv

@torchv-team/ais-mcp

English | δΈ­ζ–‡

License MCP

πŸš€ TorchV AIS Knowledge Base MCP Server

A production-ready MCP server that enables read / write / edit / file transfer operations directly on the AIS enterprise knowledge base.

img.png

Related MCP server: SAG MCP Server

✨ Features

  • πŸ“š Unified access to AIS knowledge base

  • πŸ› οΈ Full MCP toolchain (read / write / management)

  • ⚑ One-command startup via npx

  • πŸ”Œ Supports both STDIO and HTTP (streamable) transports

  • πŸ” Fine-grained permission control (readonly / write / admin)


πŸš€ Installation & Run

npx -y @torchv-team/ais-mcp

πŸ”‘ Required Configuration

Before starting, set the following environment variables:

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

🌐 How to get KB_EXECUTE_URL

πŸ“Œ Steps:

  1. Open your AIS instance

  2. Copy the site origin from the browser address bar

πŸ‘‰ Example:

https://bot.torchv.com

πŸ” How to get KB_TOKEN

Recommended:

AIS β†’ Admin Center β†’ API Keys β†’ Create Key

Temporary (not recommended for production):

Browser DevTools β†’ Network β†’ Inspect request β†’ Copy token

βš™οΈ Optional Configuration

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"}'

πŸ›‘οΈ Permission Levels

  • 🟒 readonly β†’ Read-only access

  • 🟑 write β†’ Allows write / upload / publish

  • πŸ”΄ admin β†’ Full control (move / delete)


🧩 Run Modes

πŸ–₯️ STDIO Mode (Local MCP Client)

npm run build
node dist/cli.js

or:

npm run dev
npm run start

🌍 Streamable HTTP Mode

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

or:

npm run dev:http
npm run start:http

πŸ“Œ Parameters:

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

πŸ”Œ Claude / Codex Configuration

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 Mode

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

πŸ› οΈ Tooling Overview

πŸ“– Read-only

  • kb_list_repos

  • kb_list_path

  • kb_tree

  • kb_search

  • kb_read_document

  • kb_render_link

  • kb_download_file

  • kb_get_download_link


✏️ Write

  • kb_write_document

  • kb_patch_document

  • kb_create_directory

  • kb_copy_document

  • kb_publish_document

  • kb_upload_file


πŸ”§ Admin

  • kb_move_document

  • kb_delete_document


🧠 About AIS

AIS is TorchV’s core product β€” not just a traditional knowledge base, but:

🧠 An Enterprise AI Knowledge Engine

Core Capabilities

  • πŸ”„ Transform scattered data β†’ structured knowledge

  • πŸ” Searchable

  • 🧩 Governable

  • ⚑ Composable

  • πŸ“ˆ Optimizable


🎁 Try AIS

πŸ“² Contact us (CEO WeChat):

img.png

Available Tools

8 tools
kb_download_fileD

Inputs: code (required), localPath (required), extractIs, overwrite.

kb_list_pathD

Inputs: path (required), sort, limit.

kb_list_reposD

Inputs: sort, limit.

kb_read_documentD

Inputs: code, name, range, head, +2 more.

kb_treeD

Inputs: path (required), depth, limit.

Tool Schema Changelog

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

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers