Once riskmanaged-mcp is installed, point your AI client at it. Every client
below uses the same stdio command and the same two environment variables —
only the config file location and its shape differ. Find your client and
follow its section.
Claude Desktop#
Configuration file#
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
Configuration#
{
"mcpServers": {
"riskmanaged": {
"command": "riskmanaged-mcp",
"env": {
"RISKMANAGED_TOKEN": "your_api_token_here",
"RISKMANAGED_URL": "https://agent.riskmanaged.io"
}
}
}
}Steps#
- Install riskmanaged-mcp:
pip install riskmanaged-mcp - Open Claude Desktop → Settings → Developer → Edit Config
- Paste the JSON above, replacing the token with your API token
- Restart Claude Desktop
- Look for the 🔨 hammer icon — click it to verify the RiskManaged tools appear
Cursor#
Configuration file#
~/.cursor/mcp.json
Configuration#
{
"mcpServers": {
"riskmanaged": {
"command": "riskmanaged-mcp",
"env": {
"RISKMANAGED_TOKEN": "your_api_token_here",
"RISKMANAGED_URL": "https://agent.riskmanaged.io"
}
}
}
}Steps#
- Install riskmanaged-mcp:
pip install riskmanaged-mcp - Create or edit
~/.cursor/mcp.json - Paste the configuration above
- Restart Cursor
- In the Cursor AI chat, type "Use the riskmanaged tools to list my strategies" to verify
Cursor also supports project-level MCP config in .cursor/mcp.json at the
project root.
Windsurf#
Configuration file#
| OS | Path |
|---|---|
| macOS | ~/.codeium/windsurf/mcp_config.json |
| Windows | %APPDATA%\Codeium\Windsurf\mcp_config.json |
| Linux | ~/.config/Codeium/Windsurf/mcp_config.json |
Configuration#
{
"mcpServers": {
"riskmanaged": {
"command": "riskmanaged-mcp",
"env": {
"RISKMANAGED_TOKEN": "your_api_token_here",
"RISKMANAGED_URL": "https://agent.riskmanaged.io"
}
}
}
}Steps#
- Install riskmanaged-mcp:
pip install riskmanaged-mcp - Open Windsurf → Settings (Cmd/Ctrl + ,) → Cascade → Plugins → Edit configuration
- Paste the configuration above
- Open Command Palette (Cmd/Ctrl + Shift + P) → "Reload Window"
- Verify in Cascade chat by looking for the MCP icon
VS Code#
Configuration#
VS Code supports MCP through Copilot's agent mode. Create a
.vscode/mcp.json in your project:
{
"servers": {
"riskmanaged": {
"command": "riskmanaged-mcp",
"env": {
"RISKMANAGED_TOKEN": "your_api_token_here",
"RISKMANAGED_URL": "https://agent.riskmanaged.io"
}
}
}
}Steps#
- Install riskmanaged-mcp:
pip install riskmanaged-mcp - Create
.vscode/mcp.jsonin your project root - Paste the configuration above
- Open Copilot Chat → Switch to Agent mode
- The RiskManaged tools will be available automatically
For global configuration, add to your VS Code settings.json under
"mcp.servers".
Cline#
Configuration#
Cline stores MCP config in cline_mcp_settings.json.
Steps#
Install riskmanaged-mcp:
pip install riskmanaged-mcpOpen VS Code → Cline panel → MCP Servers icon → Configure tab
Click "Configure MCP Servers" to open the config file
Add the following configuration:
{ "mcpServers": { "riskmanaged": { "command": "riskmanaged-mcp", "env": { "RISKMANAGED_TOKEN": "your_api_token_here", "RISKMANAGED_URL": "https://agent.riskmanaged.io" }, "disabled": false } } }Save and verify the server appears as connected in the Cline MCP panel
Continue.dev#
Configuration#
Continue.dev uses its own config file. Add MCP servers to your Continue configuration:
// In ~/.continue/config.json
{
"mcpServers": [
{
"name": "riskmanaged",
"command": "riskmanaged-mcp",
"env": {
"RISKMANAGED_TOKEN": "your_api_token_here",
"RISKMANAGED_URL": "https://agent.riskmanaged.io"
}
}
]
}Steps#
- Install riskmanaged-mcp:
pip install riskmanaged-mcp - Open Continue.dev settings (gear icon → config.json)
- Add the
mcpServersarray entry above - Reload your editor
Hermes#
Prerequisites#
- Hermes agent installed (
npm install -g hermes-agentor via the Nous Research installer) - Python ≥ 3.11
- A RiskManaged API token (Profile → API Tokens)
Step 1: Install the MCP package#
curl -sSL https://riskmanaged.io/install.sh | bashOr install manually:
# uv (fastest)
uv tool install riskmanaged-mcp@git+https://github.com/riskmanaged/riskmanaged-mcp.git
# pipx
pipx install git+https://github.com/riskmanaged/riskmanaged-mcp.gitStep 2: Add to Hermes config#
Edit ~/.hermes/config.yaml and add the riskmanaged entry under
mcp_servers:
mcp_servers:
riskmanaged:
command: riskmanaged-mcp
env:
RISKMANAGED_TOKEN: "your_api_token_here"
RISKMANAGED_URL: "https://riskmanaged.io"Step 3: Reload#
In your Hermes terminal session, run:
/reload-mcpNo restart needed — Hermes hot-reloads MCP server connections.
Verify#
Ask Hermes: "What tools do you have available?" — you should see 30+ RiskManaged tools listed.
Hermes uses stdio transport for local MCP servers, which is the most secure method for local agent-tool communication.
OpenClaw#
Prerequisites#
- OpenClaw daemon running (
npm install -g openclaw@latest) - Python ≥ 3.11
- A RiskManaged API token (Profile → API Tokens)
Option A: Chat command (easiest)#
Tell OpenClaw directly in your chat interface (Telegram, Discord, etc.):
install this skill: https://github.com/riskmanaged/riskmanaged-mcpOpenClaw will clone the repo, read the AGENT.md skill metadata, and
register the MCP tools automatically.
Option B: Manual skill installation#
Clone the repo into your OpenClaw
skills/directory:cd ~/.openclaw/skills git clone https://github.com/riskmanaged/riskmanaged-mcp.gitInstall the Python package:
curl -sSL https://riskmanaged.io/install.sh | bashSet your API token in OpenClaw Settings → Skills → Workspace Skills → Environment Variables:
RISKMANAGED_TOKEN= your tokenRISKMANAGED_URL=https://riskmanaged.io
Option C: MCPorter config#
If using MCPorter for MCP connections, add to your config:
{
"mcpServers": {
"riskmanaged": {
"command": "riskmanaged-mcp",
"env": {
"RISKMANAGED_TOKEN": "your_api_token_here",
"RISKMANAGED_URL": "https://riskmanaged.io"
}
}
}
}Verify#
Ask OpenClaw: "List my trading strategies" — it should call the
RiskManaged list_strategies tool and return results.
AGENT.md discovery: OpenClaw scans for AGENT.md files in skill
directories. The RiskManaged repo includes one at the root with full tool
documentation and workflow instructions.