MCP server for Viking Knowledge Base Service
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-server-knowledgebase","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Viking Knowledge Base MCP Server [简体中文](README_zh.md) ## Overview Viking Knowledge Base MCP Server lets MCP clients such as Claude Desktop, Cursor, Cline, and Trae interact with VolcEngine Viking Knowledge Base. It supports managing and inspecting collections and documents, and searching for relevant knowledge chunks. ## Features - Add a document to a knowledge base collection by URL - Get document information and processing status - List documents with cursor pagination - Get collection information and build status - List collections in the configured project - Search a collection with optional document filtering - Authenticate with either a Viking API key or VolcEngine AK/SK credentials - Run over stdio or stateless Streamable HTTP ## Prerequisites - Python 3.10 or later - A Viking Knowledge Base API key, or VolcEngine AK/SK credentials ## Installation Install from PyPI: ```bash pip install mcp-server-knowledgebase ``` Or install it as a persistent command-line tool with `uv`: ```bash uv tool install mcp-server-knowledgebase ``` For local development, clone the repository and install this package in editable mode: ```bash git clone https://github.com/volcengine/mcp-server.git cd mcp-server/server/mcp_server_knowledgebase uv pip install -e . ``` ## Configuration ### Authentication Configure at least one authentication method: - API key: set `VIKING_API_KEY`. Requests use `Authorization: Bearer <VIKING_API_KEY>`. - AK/SK: set both `VOLCENGINE_ACCESS_KEY` and `VOLCENGINE_SECRET_KEY`. Requests use VolcEngine SignerV4 authentication. When both methods are configured, `VIKING_API_KEY` takes precedence. If no API key is set, the access key and secret key must be configured together. ### Environment variables | Environment variable | Description | Default | |---|---|---| | `VIKING_API_KEY` | Viking Knowledge Base API key; takes precedence when configured | - | | `VOLCENGINE_ACCESS_KEY` | VolcEngine access key | - | | `VOLCENGINE_SECRET_KEY` | V…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.