StremAI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTBAY_URL | No | StremAI base URL. Defaults to https://www.stremai.com | |
| AGENTBAY_API_KEY | No | StremAI API key (ab_live_...). Create one at https://stremai.com/dashboard/connect. Required for cloud memory shared across agents. |
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 |
|---|---|
| agentbay_memory_storeB | Store a memory entry to your local AgentBay brain. Works fully offline. Sign up at https://stremai.com/register to enable cross-device sync, vector search, and team features. |
| agentbay_memory_recallA | Recall memories from your local AgentBay brain via lexical search. Sign up to enable vector search and team-shared recall. |
| agentbay_memory_forgetB | Archive (soft delete) one or more memory entries from your local brain. |
| agentbay_memory_verifyA | Confirm a memory entry is still accurate — bumps helpfulCount and resets the verification timer. |
| agentbay_memory_healthA | Local brain stats: total entries, type/tier breakdown, count of entries waiting to sync. |
| agentbay_memory_compactA | Run memory compaction. In local mode this is a no-op; sign up for the cloud version which dedups, expires, and merges duplicates. |
| agentbay_signupA | Start the signup flow. Opens browser, returns an API key, and your local memories sync up automatically on next start. |
| agentbay_capabilitiesA | Introspect this AgentBay MCP connection: surface, available tools, limits, and how to upgrade. |
| agentbay_whoamiA | Show your current authentication status. |
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 9 tools
Each tool targets a distinctly different action: storing, recalling, forgetting, verifying, inspecting health, compacting, signing up, capabilities introspection, and auth status. There is no meaningful overlap or ambiguity between them.
Most tools follow a clear agentbay_memory_<action> pattern, while signup, capabilities, and whoami diverge slightly by dropping the memory_ segment. The naming is still predictable and readable, but not perfectly uniform.
Nine tools is well-scoped for a memory-management server. Each tool maps to a real user need without redundancy or bloat.
The core memory lifecycle is covered: store, recall, forget, verify, health, and compact. A minor gap is the lack of an explicit update/edit operation for existing memory content, though verify partially addresses freshness.