AI Agents
NanoClaw
A small open-source personal agent that runs each group's work in its own container.
- Connects with
- API key, Skill
- Plans
- Free and open source.
Before you start
- NanoClaw installed, with OneCLI, its credential gateway, set up.
- An API key, created in SPREVA under Developer, then API keys.
Set it up
- 1
Store your SPREVA API key in OneCLI, for SPREVA's address only. OneCLI adds it to every request to SPREVA, so your agents never see it:
Terminal onecli secrets create --name SPREVA --type generic \ --value "$SPREVA_API_KEY" --host-pattern app.spreva.ai \ --header-name Authorization --value-format "Bearer {value}" - 2
Give the secret to the agent group that should use SPREVA, as NanoClaw's credentials guide shows.
- 3
Find the group's id with
ncl groups list, then add SPREVA to the group and approve the change:Terminal ncl groups config add-mcp-server --id <group-id> \ --name spreva --url https://app.spreva.ai/api/mcp - 4
Restart the group so its agents load SPREVA, and approve the restart:
Terminal ncl groups restart --id <group-id>
Also works with
- The CLI and the Agent Skill
Install the
sprevacommand line and its Agent Skill, for agents that work in a terminal.Terminal export SPREVA_API_KEY=spreva_sk_... npx -y @spreva/cli skill install --dir container/skills
Check it works
Start a new conversation and ask:
What's going out this week on SPREVA?
NanoClaw calls SPREVA's overview tool and answers with the workspace's time zone, what goes out next and anything that needs attention. The first time, NanoClaw may ask you to allow the tool.
Good to know
- Run the Agent Skill command in your NanoClaw folder. It puts the skill in
container/skills, which every group reads.
Troubleshooting
SPREVA isn't there after adding it
Adding a server and restarting a group both wait for your approval. Approve both, and SPREVA loads when the group restarts.
Something else? Troubleshooting covers sign-in loops, plans, limits and time zones.