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)
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。