A store you can only read from leaves a gap: the useful passage from today's conversation never reaches it. Here writing is a call, so a collection can grow out of ordinary work — and the two description calls exist so an agent can check what it is pointed at before either operation.
A read and write path to a VikingDB collection. Text goes in for later retrieval and comes back by similarity, and the collection and index it works against are fixed at launch.
- Information written into the collection for later use
- Similarity search over what has been stored
- A description of the collection you are pointed at
- A description of the index behind it
A VikingDB collection and index, plus the host, region, access key and secret key for the service. All six are passed on the launch command, and uv on your PATH runs it.
One command plus a key — npx -y @smithery/cli install mcp-server-vikingdb --client claude, then supply credentials
