robrain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERCEPTION_API_KEY | No | Perception API key (generated by `npx robrain up`). Optional — read from ~/.robrain/config.json when present. | |
| PERCEPTION_API_URL | No | URL of your self-hosted Perception backend (started with `npx robrain up`). Optional — read from ~/.robrain/config.json when present. | http://localhost:3001 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sensing_start_sessionA | Signal the start of a new Claude Code session. Call this once at the beginning of every session. Returns the always-on project summary to inject into your context. session_id may be omitted or empty — the server generates a unique id and returns it (use that id for sensing_record_turn and sensing_end_session). |
| sensing_record_turnA | Record a completed conversation turn (user message + Claude reply). Call this after every exchange. Survives server restarts — keep using the same session_id even if the server reconnected mid-conversation. Returns whether a topic shift was detected — if true, call your context injection tool. |
| sensing_end_sessionA | Signal the end of a Claude Code session. Triggers the flush-on-close hook to ship any unclassified buffered turns to Perception before the session closes. |
| sensing_get_statusA | Get the current status of the Sensing buffer for a session. Useful for debugging. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: start session, record turn, get status, end session. No overlap or confusion.
All tools follow the consistent pattern 'sensing_verb_noun' using snake_case, making them predictable.
Four tools cover the essential session lifecycle (start, record, status, end) without unnecessary extras.
The tool set fully covers session management for sensing, including turn recording and topic shift detection, with no obvious gaps.