okovia-mcp

OkOvia MCP server — ask any MCP client (Claude Desktop, Claude Code, …) about the cost, margin, reliability, and quality of your AI usage, in natural language.

It talks to the OkOvia API with your key and exposes the read dashboards as MCP tools. It runs on your machine; no data beyond the API calls leaves it, and it never sends prompts or content.

What you can ask

• "How much did my AI features cost, highest first?"
• "Which model or provider is driving the cost?"
• "Show the most recent operations and their cost. Detail op_7K9x."
• "What's my reliability — which model has the most errors or timeouts?"
• "Compare the models I use."

Requirements

• Python 3.10+ (run via uvx or pipx)
• An OkOvia secret API key (vik_sec_…) from the console → Settings → Service accounts

Configure your MCP client

Claude Desktop / Claude Code (mcpServers block):

{
  "mcpServers": {
    "okovia": {
      "command": "uvx",
      "args": ["okovia-mcp"],
      "env": {
        "OKOVIA_API_KEY": "vik_sec_your_key",
        "OKOVIA_ENDPOINT": "https://api.okovia.com"
      }
    }
  }
}

OKOVIA_ENDPOINT defaults to https://api.okovia.com — set it only for self-hosted deployments.

Tools

Everything is scoped to the workspace/project the API key belongs to — the server passes no ids of its own.

Security

Use a read-only key (vik_read_..., create one on the console's API Keys page): it can query dashboards and reports but can never submit events or manage anything — if it leaks, your data can be read but not touched. Secret keys still work for backwards compatibility, but carry admin scope; prefer rotating to a read key.

Development

pip install -e ".[dev]"
pytest            # client tests — stdlib only, no MCP runtime or network needed

client.py is stdlib-only and independently tested; server.py wires those methods as MCP tools via the official mcp SDK.

MIT licensed. Part of OkOvia.