OpenViking Grok MCP Proxy
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenViking Grok MCP Proxyrecall what I know about the deployment process"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
/mcpendpointReads 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)
Related MCP server: waypath
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 … --trustEnable 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' \
--yesLocal unauthenticated server:
./install.sh --url 'http://127.0.0.1:1933' --api-key '' --yes --localInstall 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 openvikingOr from a checkout:
git clone https://github.com/shpaw415/openviking-grok-plugin.git
cd openviking-grok-plugin
./install.sh --local --yesMCP-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.mjsVerify
grok mcp doctor openviking
# In a session:
# /ov → status report
# /mcps → openviking readyAsk Grok:
Use the openviking MCP: run health, then list
viking://resources.
What you get
Component | Path | Purpose |
MCP proxy |
| stdio bridge to OpenViking |
Status |
| Health, identity, toggles |
Skill |
| When/how to use the tools |
Rule |
| 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 |
| Proxy + plugin debug logs under |
| Stable peer id for multi-workspace isolation |
| 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 afterwardUninstall
bash <(curl -fsSL https://raw.githubusercontent.com/shpaw415/openviking-grok-plugin/main/install.sh) --uninstall
# or
grok plugin uninstall openviking --confirmovcli.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 --yesProxy 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.mjsRelationship 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
Grok plugins guide (Plugins / MCP)
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceEnables AI tools like GitHub Copilot to manage and persist context using a local JSON-based memory store. Provides CLI, MCP server, and VS Code integration for storing, retrieving, and managing context entries.Last updated2
- AlicenseAqualityBmaintenanceLocal-first external brain for Claude Code, Codex, and any MCP client. Stores decisions, entities, and session artifacts in one SQLite file and exposes MCP tools for recall, page, promote, review, graph-query, and source-status.Last updated1194MIT
- AlicenseCqualityBmaintenanceBridges MCP clients with local Codex CLI to execute autonomous coding tasks, manage threads, and inspect history via SQLite state.Last updated138734Apache 2.0
- AlicenseBqualityCmaintenanceLocal Markdown-backed memory tools for Codex and other MCP-capable agents. Exposes durable agent knowledge via CLI and MCP server.Last updated5MIT
Related MCP Connectors
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shpaw415/openviking-grok-plugin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server