OpenViking Grok MCP Proxy
Bridges Grok CLI to an OpenViking context database over MCP, enabling memory and code tools like recall, search, and resource management.
README
OpenViking MCP Plugin for Grok CLI
Connect Grok CLI / Grok Build to an OpenViking context database.
The plugin ships a stdio → HTTP MCP proxy that:
- Starts as a local MCP server inside Grok
- Forwards JSON-RPC to your OpenViking server’s
/mcpendpoint - Reads credentials from
~/.openviking/ovcli.conforOPENVIKING_*env vars
(no API key pasted into~/.grok/config.toml)
You get the full OpenViking tool surface: health, find, search, recall, remember, list, read, glob, grep, code tools, add_resource, and more.
Requirements
- Grok CLI installed and logged in (
grok login) - Node.js 18+
- A reachable OpenViking server (local or hosted)
Quick install
bash <(curl -fsSL https://raw.githubusercontent.com/shpaw415/openviking-grok-plugin/main/install.sh)
The installer will:
- Write or update
~/.openviking/ovcli.conf(URL + API key) - Run
grok plugin install … --trust - Enable the plugin
Non-interactive
bash <(curl -fsSL https://raw.githubusercontent.com/shpaw415/openviking-grok-plugin/main/install.sh) \
--url 'https://your-openviking.example.com' \
--api-key 'YOUR_KEY' \
--yes
Local unauthenticated server:
./install.sh --url 'http://127.0.0.1:1933' --api-key '' --yes --local
Install without the script
# 1. Credentials
mkdir -p ~/.openviking
cat > ~/.openviking/ovcli.conf <<'EOF'
{
"url": "https://your-openviking.example.com",
"api_key": "YOUR_KEY"
}
EOF
chmod 600 ~/.openviking/ovcli.conf
# 2. Plugin
grok plugin install shpaw415/openviking-grok-plugin --trust
grok plugin enable openviking
Or from a checkout:
git clone https://github.com/shpaw415/openviking-grok-plugin.git
cd openviking-grok-plugin
./install.sh --local --yes
MCP-only (absolute path, no plugin manager)
Useful if you prefer config.toml registration:
./install.sh --local --mcp-only --yes
# → grok mcp add openviking -- node /path/to/servers/mcp-proxy.mjs
Verify
grok mcp doctor openviking
# In a session:
# /ov → status report
# /mcps → openviking ready
Ask Grok:
Use the openviking MCP: run health, then list
viking://resources.
What you get
| Component | Path | Purpose |
|---|---|---|
| MCP proxy | servers/mcp-proxy.mjs |
stdio bridge to OpenViking /mcp |
| Status | /ov command |
Health, identity, toggles |
| Skill | skills/openviking |
When/how to use the tools |
| Rule | rules/openviking.md |
Prefer recall over guessing |
Configuration
Priority (highest → lowest):
- Environment:
OPENVIKING_URL/OPENVIKING_BASE_URL,OPENVIKING_API_KEY/OPENVIKING_BEARER_TOKEN,OPENVIKING_ACCOUNT,OPENVIKING_USER ~/.openviking/ovcli.conf(orOPENVIKING_CLI_CONFIG_FILE)~/.openviking/ov.conf(legacy server config)- Default
http://127.0.0.1:1933
Example ovcli.conf:
{
"url": "https://openviking.example.com",
"api_key": "…",
"account": "optional-team",
"user": "optional-user"
}
Optional:
| Variable | Effect |
|---|---|
OPENVIKING_DEBUG=1 |
Proxy + plugin debug logs under ~/.openviking/logs/ |
OPENVIKING_PEER_ID |
Stable peer id for multi-workspace isolation |
OPENVIKING_WORKSPACE_PEER=0 |
Disable workspace-derived peer |
Do not put the bearer token in [mcp_servers.openviking.headers] if you use this plugin — the proxy already authenticates. If you previously added a raw HTTP MCP entry in config.toml, remove or disable it to avoid two servers with the same tools:
grok mcp remove openviking # only if it was the old HTTP entry
# reinstall via this plugin afterward
Uninstall
bash <(curl -fsSL https://raw.githubusercontent.com/shpaw415/openviking-grok-plugin/main/install.sh) --uninstall
# or
grok plugin uninstall openviking --confirm
ovcli.conf is kept so other harnesses (Claude Code, Cursor, …) keep working.
Development
git clone https://github.com/shpaw415/openviking-grok-plugin.git
cd openviking-grok-plugin
grok plugin validate .
./install.sh --local --yes
Proxy smoke test (credentials required):
# Initialize handshake over stdio (partial)
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}' \
| node servers/mcp-proxy.mjs
Relationship to upstream OpenViking
The stdio proxy core is adapted from the official OpenViking memory plugins (examples/memory-plugin-shared, examples/claude-code-memory-plugin), licensed Apache-2.0. This repository packages a Grok CLI–first distribution with an installer and Grok plugin manifest (.grok-plugin/plugin.json).
Upstream also ships Claude Code, Codex, Cursor, and other harness plugins. Use those installers for non-Grok agents:
bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)
License
Apache-2.0 — see LICENSE.
Links
- OpenViking
- OpenViking docs
- Grok plugins guide (Plugins / MCP)
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.