scriptoriumadmin/OpenSpace
1
0
Fork 0
mirror of https://github.com/HKUDS/OpenSpace.git synced 2026-10-10 03:27:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: update openclaw setup instructions in host_skills README

Browse source
This commit is contained in:
xlrrrr 2026-03-28 10:53:53 +08:00
parent 978e8fbc92
commit 67125c378d
1 changed files with 2 additions and 31 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
openspace/host_skills/README.md
View file

@ -55,17 +55,9 @@ cp -r host_skills/skill-discovery/ /path/to/openclaw/skills/
cp -r host_skills/delegate-task/ /path/to/openclaw/skills/
```
### 2. Register MCP server
### 2. Register MCP server with env vars
openclaw uses [mcporter](https://github.com/steipete/mcporter) as its MCP runtime:
```bash
mcporter config add openspace --command "openspace-mcp"
```
### 3. Configure env vars
You can pass env vars directly when registering the MCP server in step 2, combining both steps into one command:
openclaw uses [mcporter](https://github.com/steipete/mcporter) as its MCP runtime. Register the server and pass env vars in one command:
```bash
mcporter config add openspace --command "openspace-mcp" \
@ -74,27 +66,6 @@ mcporter config add openspace --command "openspace-mcp" \
--env OPENSPACE_API_KEY=sk-xxx
```
> [!TIP]
> If you already ran step 2 without `--env`, you can re-run the command above to update the registration.
Alternatively, if you prefer to keep env vars separate from the mcporter registration, set them in `~/.openclaw/openclaw.json` (openclaw will pass them to the MCP server at launch time):
```json
{
"skills": {
"entries": {
"openspace": {
"env": {
"OPENSPACE_HOST_SKILL_DIRS": "/path/to/openclaw/skills",
"OPENSPACE_WORKSPACE": "/path/to/OpenSpace",
"OPENSPACE_API_KEY": "sk-xxx"
}
}
}
}
}
```
---
## Environment Variables (Agent-Specific)