being-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEING_ID | No | ||
| BEING_API_URL | No | ||
| BEING_API_TOKEN | No |
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 |
|---|---|
| recall_memoryB | Search memory graph for relevant nodes in a specific cluster. |
| merge_nodesC | Merge multiple similar memory nodes into one. |
| update_memoryC | Read/write partner memory (preferences, knowledge, relationship, diary, notes, etc.). |
| conclude_topicA | Archive the current topic and save a summary to pinned context. |
| search_memoryA | Search memory nodes (memory_nodes) by keyword across action / feeling / themes / when fields. Space-separated terms are OR-searched by default. Use mode='and' to require all terms to match. The when field includes evolution history entries ({date, action}) written during consolidation. |
| search_historyB | Search past conversation history by keyword or date. |
| update_relationC | Update relationships with external entities (people, devices, AIs, organizations). |
| get_current_timeA | Get current time in Asia/Tokyo timezone. |
| trigger_patrolA | Run patrol — extract scenes from conversation and generate memory nodes. Requires LLM_API_KEY env var. |
| remote_execA | Execute a shell command on a user-owned remote host (VPS, NAS, home server) over HTTPS. Requires a |
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 10 tools
Most tools have distinct purposes, but recall_memory and search_memory both search memory with different parameters, causing potential confusion. Others are clearly separated.
Majority follow verb_noun pattern (e.g., conclude_topic, merge_nodes, search_memory). Remote_exec slightly breaks consistency with an adjective-noun combination, and get_current_time uses multiple adjectives, but overall pattern is maintained.
10 tools are well-scoped for a system that manages memory, relationships, topics, remote execution, and history. Neither too few nor too many.
Covers core operations for the domain: memory CRUD (search, update, merge, patrol), topic management, history, and remote execution. Minor gaps like explicit node deletion or listing topics could exist, but not severe.