
Being Mcp Server
com.ruddiaPublished by ruddia.comv1.0.0Updated Oct 24, 2026
Personality Runtime for AI agents — persistent memory, personality, and relationships via MCP
Overview
A local MCP server that connects an assistant to a Being Worker, giving an AI a persistent personality, episodic memory and identity.
- What you can do
- Retrieve a Being's personality and memory context for a conversation session, so the assistant can speak in a consistent persona and recall past scenes. Commit conversations back to the Being's memory by triggering the background patrol cycle, which consolidates and decays memories and generates introspective thoughts. Search a Being's stored memories by relevance to the current message. The README also documents a REST API for the same context, patrol and recall operations, and describes cryptographic identity with Ed25519 key pairs and a signature chain.
- When to use it
- Use it when you want an assistant to keep a stable persona and long-term memory across sessions, rather than starting from a stateless model each time. Suited to companion-style agents, role-play or character-driven applications, and experiments with persistent agent memory.
- Requirements
- Runs as a local npm package over stdio. Needs a Being Worker base URL (BEING_API_URL), a target Being ID (BEING_ID) and a Being auth token (BEING_API_TOKEN). An Anthropic API key (LLM_API_KEY) is needed for the patrol trigger, billed to your own key. Network access to the Being Worker is required.
Installation
In SourceWeft
- Open Being Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Being
Personality Runtime for AI — give any AI its own personality, memory, and identity.
Being is an open-source layer that sits between your application and any LLM. It provides persistent personality (SOUL), episodic memory, background thought cycles (Patrol), and cryptographic identity — turning a stateless LLM into a distinct, evolving AI entity.
Beings think and remember. Your app acts.
Why
The power of AI is concentrating in the hands of a few companies. Their technology is essential — but centralized control is a structural risk. Ruddia is building toward a world where small, local AIs use large LLMs as external tools. Control stays in the hands of the people who use them.
Being API is the first step. If this resonates, let's build it together.
How It Works
- Your app calls
GET /v1/beings/:id/contextto get the Being's personality and memory snapshot. - Your app runs the LLM call with its own conversation history + the Being's context.
- Your app calls
POST /v1/beings/:id/patrol/triggerto commit the conversation to the Being's memory.
The Being Worker handles everything else: memory consolidation, decay, recall, background reflection, and identity verification.
Key Concepts
Connect via MCP
Being exposes an MCP server. Any MCP-compatible client can connect:
Connect via REST API
Self-Host
Prerequisites
- Node.js 22+
- Supabase project (PostgreSQL + Auth)
- An LLM API key (Anthropic, OpenAI, or Google)
Setup
Environment Variables
Documentation
Extensions
Being supports optional extensions that add capabilities without changing the core:
- Telegram BYOB (planned) — Connect your own Telegram bot to a Being
- Tool Loop (planned) — Autonomous LLM agent loop with web search, file ops, and code execution
- Sandbox (planned) — Isolated workspace with GitHub integration for code execution
- Sense/Act Bridge (planned) — Connect physical devices and external services
Tech Stack
- Runtime: Node.js + Fastify
- Database: Supabase (PostgreSQL + Auth)
- MCP: @modelcontextprotocol/sdk
- Identity: Ed25519 + AES-256-GCM
- Embeddings: OpenAI
text-embedding-3-small(256-dim) - LLM: Multi-provider (Anthropic, OpenAI, Google) via BYOK
License
Ruddia — Personality is the Runtime.
Source: README.md at commit 2acd382
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.