openviking-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENVIKING_URL | No | OpenViking server base URL | http://127.0.0.1:1933 |
| OPENVIKING_API_KEY | No | Sent as X-API-Key when set; leave empty for loopback dev auth | |
| OPENVIKING_TIMEOUT_MS | No | Per-request timeout in milliseconds | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ov_searchA | Search the OpenViking knowledge base by meaning. Returns matching documents with their URI, relevance score and a short summary. Use it before writing SQL, DDL or node changes to check for existing standards and known pitfalls. |
| ov_readA | Read the full text of one OpenViking document by URI (L2 content). Use it after ov_search when a hit looks relevant and you need the complete section. |
| ov_overviewA | Inspect OpenViking directory structure with generated summaries (L0/L1). Use it to survey what knowledge exists before deciding what to search or read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools are clearly separated by purpose: ov_overview surveys structure, ov_search finds relevant documents semantically, and ov_read retrieves full text by URI. Their descriptions explicitly describe a progression, leaving little chance of misselection.
All tools use the same ov_ prefix followed by a concise action-oriented suffix: search, read, overview. The naming is predictable and easy to scan.
Three tools are well-scoped for a read-only knowledge-base MCP. Each operation covers a distinct stage of discovery and retrieval without redundant surface area.
The set covers the full retrieval lifecycle: survey available knowledge, search by meaning, then read full content. No obvious read-side gaps exist, and write operations are not implied by the server's purpose.