Installation Guide
This guide covers installing Orchex and configuring it as an MCP server for Claude Desktop, Cursor, Windsurf, and other MCP-compatible clients.
Prerequisites
- Node.js 18 or higher
- npm package manager
- An LLM API key (Anthropic, OpenAI, Gemini, DeepSeek, or Ollama)
- An MCP-compatible client (Claude Desktop, Cursor, Windsurf, Claude Code, etc.)
Quick Start
1. Install Orchex
npm install -g @wundam/orchexOr install locally in your project:
npm install @wundam/orchex2. Verify Installation
orchex --versionYou should see the current version number (e.g., 1.0.0-rc.1).
3. Set Up Your API Key
Set an environment variable for your LLM provider:
# Pick one:
export ANTHROPIC_API_KEY=sk-ant-...
export OPENAI_API_KEY=sk-...
export GEMINI_API_KEY=...
export DEEPSEEK_API_KEY=sk-...Important: Never commit API keys to version control.
MCP Server Configuration
Orchex can be used as an MCP (Model Context Protocol) server, allowing AI assistants to orchestrate complex multi-step workflows.
Claude Desktop
Locate your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- macOS:
Add Orchex to the MCP servers section:
{
"mcpServers": {
"orchex": {
"command": "npx",
"args": ["-y", "@wundam/orchex"]
}
}
}Restart Claude Desktop
Verify: Start a new conversation and ask Claude to list available Orchex tools. You should see tools like
init,execute,status,learn, etc.
Cursor
Open Cursor Settings (Cmd/Ctrl + ,)
Navigate to Features → Model Context Protocol
Add a new MCP server:
{
"orchex": {
"command": "npx",
"args": ["-y", "@wundam/orchex"]
}
}- Restart Cursor
Windsurf
Open Windsurf Settings
Navigate to MCP Servers configuration
Add Orchex:
{
"mcpServers": {
"orchex": {
"command": "npx",
"args": ["-y", "@wundam/orchex"]
}
}
}- Restart Windsurf
Using a Local Installation
If you installed Orchex locally in your project:
{
"mcpServers": {
"orchex": {
"command": "node",
"args": ["./node_modules/@wundam/orchex/bin/orchex.js"]
}
}
}Environment Variables
Orchex auto-detects your LLM provider from environment variables. Set one of:
ANTHROPIC_API_KEY— Anthropic ClaudeOPENAI_API_KEY— OpenAI (GPT-4, GPT-4.1)GEMINI_API_KEY— Google GeminiDEEPSEEK_API_KEY— DeepSeekOLLAMA_HOST— Ollama (local models)
You can pass these via the MCP config env field:
{
"env": {
"ANTHROPIC_API_KEY": "sk-ant-your-key-here"
}
}To switch providers, use orchex config --provider <name>.
Verification Steps
Test CLI Installation
# Check version
orchex --version
# View current config
orchex config --showTest MCP Server
In Claude Desktop/Cursor/Windsurf, start a new conversation
Ask: "Can you list the available Orchex tools?"
You should see tools like:
init— Initialize an orchestrationexecute— Run the orchestrationstatus— Check progresslearn— Parse a plan into streamscomplete— Archive orchestration
Try a test orchestration:
Use orchex.init to create a simple orchestration with one stream that creates a hello.ts file, then execute it.
Troubleshooting
"orchex: command not found"
- Ensure Node.js and npm are installed:
node --version && npm --version - If globally installed, check npm global bin path:
npm bin -g - Add npm global bin to PATH or install locally instead
"API key not found" or Authentication Errors
- Verify your
ANTHROPIC_API_KEYis set correctly - Check for typos in your API key
- Ensure the environment variable is accessible in your MCP config
- Test your API key directly:
curl https://api.anthropic.com/v1/messages -H "x-api-key: $ANTHROPIC_API_KEY"
MCP Server Not Appearing in Client
- Verify the config file path is correct for your OS
- Check JSON syntax (use a JSON validator)
- Ensure
npxis available:npx --version - Check client logs for error messages
- Restart the client application completely
"Module not found" Errors
- Clear npm cache:
npm cache clean --force - Reinstall:
npm uninstall -g @wundam/orchex && npm install -g @wundam/orchex - Check Node.js version:
node --version(must be 18+)
Workflow Execution Failures
- Validate your manifest:
orchex validate manifest.yaml - Check logs with
DEBUG=orchex:* orchex execute manifest.yaml - Verify all required tools/commands are installed
- Check file permissions for read/write operations
Enable Debug Logging
For detailed troubleshooting:
# CLI
DEBUG=orchex:* orchex execute manifest.yaml
# MCP Server - add to env in config:
{
"env": {
"DEBUG": "orchex:*",
"ANTHROPIC_API_KEY": "..."
}
}Next Steps
- Read the Quick Start Guide for your first workflow
- Explore Example Workflows for common patterns
- Learn about Manifest Format for advanced configurations
- Check out Best Practices for optimal results
Updating Orchex
# Global installation
npm update -g @wundam/orchex
# Local installation
npm update @wundam/orchex
# Check for updates
npm outdated -g @wundam/orchexUninstallation
# Global installation
npm uninstall -g @wundam/orchex
# Local installation
npm uninstall @wundam/orchex
# Remove MCP server config from your client
# (edit the claude_desktop_config.json or equivalent)Getting Help
- Documentation: Full documentation
- Examples: See the examples/ directory
- Issues: Report bugs at orchex.dev/support
- Community: Join our Discord/Slack for support
Need help? If you encounter any issues during installation, please check our troubleshooting section or reach out for support.