Fire in da houseTop Tip:Paying $100+ per month for Perplexity, MidJourney, Runway, ChatGPT and other tools is crazy - get all your AI tools in one site starting at $15 per month with Galaxy AI Fire in da houseCheck it out free

vikingdb-mcp-server

MCP.Pizza Chef: KashiwaByte

The vikingdb-mcp-server is a specialized MCP server designed to integrate with VikingDB, a high-performance vector database developed by ByteDance. It enables efficient storage, upsertion, and search of vectorized information through a set of dedicated tools such as collection introduction, index introduction, data upsertion, and search capabilities. Configurable with host, region, and access credentials, this server facilitates seamless interaction with VikingDB for advanced vector data management and retrieval within the MCP ecosystem.

Use This MCP server To

Store vector data efficiently in VikingDB Search vectorized information with high performance Upsert new data into VikingDB collections Introduce and manage VikingDB collections Explain VikingDB index structures for optimization

README

VikingDB MCP server

smithery badge an mcp server for vikingdb store and search

What is VikingDB

VikingDB is a high-performance vector database developed by ByteDance.

You can easily use it following the doc bellow: https://www.volcengine.com/docs/84313/1254444

Tools

The server implements the following tools:

  • vikingdb-colleciton-intro: introduce the collection of vikingdb

  • vikingdb-index-intro: introduce the index of vikingdb

  • vikingdb-upsert-information: upsert information to vikingdb for later use

  • vikingdb-search-information: searche for information in the VikingDB

Configuration

  • vikingdb_host: The host to use for the VikingDB server.

  • vikingdb_region: The region to use for the VikingDB server.

  • vikingdb_ak: The Access Key to use for the VikingDB server.

  • vikingdb_sk: The Secret Key to use for the VikingDB server.

  • collection_name: The name of the collection to use.

  • index_name: The name of the index to use.

Quickstart

Install

Installing via Smithery

To install VikingDB MCP server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install mcp-server-vikingdb --client claude
Claude Desktop

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows: %APPDATA%/Claude/claude_desktop_config.json

Development/Unpublished Servers Configuration

{
  "mcpServers": {
    "mcp-server-vikingdb": {
      "command": "uv",
      "args": [
        "--directory",
        "dir to mcp-server-vikingdb",
        "run",
        "mcp-server-vikingdb",
        "--vikingdb-host", 
        "your host",
        "--vikingdb-region", 
        "your region",
        "--vikingdb-ak", 
        "your access key",
        "--vikingdb-sk", 
        "your secret key",
        "--collection-name",
        "your collection name",
        "--index-name",
        "your index name"
      ]
    }
  }
}

Published Servers Configuration

{
  "mcpServers": {
    "mcp-server-vikingdb": {
      "command": "uvx",
      "args": [
        "mcp-server-vikingdb",
        "--vikingdb-host", 
        "your host",
        "--vikingdb-region", 
        "your region",
        "--vikingdb-ak", 
        "your access key",
        "--vikingdb-sk", 
        "your secret key",
        "--collection-name",
        "your collection name",
        "--index-name",
        "your index name"
    ]
   }
  }
} 

Development

Building and Publishing

To prepare the package for distribution:

  1. Sync dependencies and update lockfile:
uv sync
  1. Build package distributions:
uv build

This will create source and wheel distributions in the dist/ directory.

  1. Publish to PyPI:
uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:

  • Token: --token or UV_PUBLISH_TOKEN
  • Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory dir_to_mcp_server_vikingdb run mcp-server-vikingdb --vikingdb-host your_host --vikingdb-region your_region --vikingdb-ak your_access_key --vikingdb-sk your_secret_key --collection-name your_collection_name --index-name your_index_name

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

vikingdb-mcp-server FAQ

How do I configure the vikingdb-mcp-server to connect to my VikingDB instance?
You configure it by setting the vikingdb_host, vikingdb_region, vikingdb_ak (Access Key), and vikingdb_sk (Secret Key) parameters to match your VikingDB server credentials and location.
What tools does the vikingdb-mcp-server provide?
It provides tools for collection introduction, index introduction, upserting information, and searching information within VikingDB.
Can the vikingdb-mcp-server handle real-time data updates?
Yes, it supports upserting information to VikingDB, allowing real-time or batch updates to your vector data store.
Is the vikingdb-mcp-server compatible with multiple MCP hosts?
Yes, as an MCP server, it can be integrated with any MCP client or host that supports the MCP protocol.
How secure is the connection to VikingDB through this MCP server?
Security depends on proper configuration of access keys and secret keys. The server uses these credentials to authenticate securely with VikingDB.
Where can I find documentation for VikingDB to better use this MCP server?
Official VikingDB documentation is available at https://www.volcengine.com/docs/84313/1254444 for detailed usage and configuration guidance.
Can this MCP server be used with LLM providers like OpenAI, Claude, or Gemini?
Yes, it can be integrated into workflows using these LLM providers to enhance vector search and storage capabilities.
Does the server support multiple collections within VikingDB?
Yes, you can specify the collection_name parameter to manage different collections within VikingDB.