sensorium-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug-level logging | |
| MCP_HTTP_BIND | No | Bind address for HTTP server | 127.0.0.1 |
| MCP_HTTP_PORT | No | Enable HTTP transport on this port (required for multi-thread spawning) | |
| OPENAI_API_KEY | No | For voice transcription (Whisper), TTS, and memory consolidation | |
| TELEGRAM_TOKEN | Yes | Telegram Bot API token | |
| AUTONOMOUS_MODE | No | Enable autonomous agent behavior | false |
| MCP_HTTP_SECRET | No | Shared secret for HTTP transport auth (recommended when MCP_HTTP_PORT is set) | |
| NARRATIVE_MODEL | No | Model for narrative generation (falls back to CONSOLIDATION_MODEL) | |
| REFLECTION_MODEL | No | Model for reflection pipeline (falls back to CONSOLIDATION_MODEL) | |
| TELEGRAM_CHAT_ID | Yes | Forum supergroup chat ID | |
| VOICE_ANALYSIS_URL | No | Voice emotion analysis microservice URL | |
| CONSOLIDATION_MODEL | No | OpenAI model for memory consolidation | gpt-4o |
| DMN_ACTIVATION_HOURS | No | Hours of idle before DMN reflection fires | 4 |
| WAIT_TIMEOUT_MINUTES | No | How long wait_for_instructions blocks (minutes) | 1440 |
| CONSOLIDATION_ENABLED | No | Set to 'false' to disable sending episodes to OpenAI for consolidation | true |
| TELEGRAM_SUPERVISOR_TOKEN | No | Separate bot token for supervisor DM commands (avoids 409 conflict) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/andriyshevchenko/sensorium-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server