Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From oh-mcp
Sets up Open Horizons MCP server for Claude Code: checks/configures API key, registers via claude mcp add with npx, requires restart for tools like oh_get_contexts.
npx claudepluginhub open-horizon-labs/bottle --plugin oh-mcpHow this command is triggered — by the user, by Claude, or both
Slash command
/oh-mcp:setupFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Setup Open Horizons MCP Set up the Open Horizons MCP server for strategic alignment integration. **Execute these steps in order:** ## Step 1: Check for existing API key config Check if `~/.config/openhorizons/config.json` exists and has an api_key: If the file exists and has a valid api_key, skip to Step 3. If not configured, check if `sg` (superego CLI) is available: **If sg is available:** Tell the user to run `sg setup-oh` in their terminal. This will: - Open browser to get API key - Prompt them to paste the key - Create the config file **If sg is NOT available:** Ask the use...
/setup-mcpGuides interactive MCP server setup wizard: checks prerequisites like uvx, backs up configs, verifies plugin installation, configures optional API keys.
/use-mcpInvokes the MCP command as defined in .claude/commands/use-mcp.md, enabling MCP usage within Claude Code.
/setupConfigures Tavily MCP server with your API key: checks status, guides acquisition, validates format, updates config file, and confirms with restart instructions.
/setupConfigures deliberation with MCP servers for GPT (Codex), Gemini, Grok, and OpenRouter. Seeds config, checks provider CLIs, installs orchestration rules, and prints status.
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
Share bugs, ideas, or general feedback.
Set up the Open Horizons MCP server for strategic alignment integration.
Execute these steps in order:
Check if ~/.config/openhorizons/config.json exists and has an api_key:
cat ~/.config/openhorizons/config.json 2>/dev/null
If the file exists and has a valid api_key, skip to Step 3.
If not configured, check if sg (superego CLI) is available:
which sg
If sg is available: Tell the user to run sg setup-oh in their terminal. This will:
If sg is NOT available: Ask the user for their API key, then create the config:
mkdir -p ~/.config/openhorizons
Then write to ~/.config/openhorizons/config.json:
{
"api_key": "<USER_PROVIDED_KEY>",
"api_url": "https://app.openhorizons.me"
}
Tell them to get a key from https://app.openhorizons.me/settings/api-keys if they don't have one.
Use the claude mcp add command to register the server with npx (works across all Node.js versions):
claude mcp add oh-mcp --scope user -- npx -y @cloud-atlas-ai/oh-mcp-server
This adds oh-mcp to ~/.claude.json so it's available across all projects. Using npx ensures it works regardless of which Node.js version each project uses.
Tell the user:
oh_get_contexts - List workspacesoh_get_endeavors - Browse endeavorsoh_log_decision - Log decisionsoh_about - Test the connection