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

VerifiedSTDIODesktop onlyKnowledge & MemoryAI & ML

Overview

AI-generated 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.
Before you install
Requires a secret auth token and an LLM API key; the LLM key is used for your own account, so patrol triggers may incur provider charges. Conversations are sent to the Being Worker and stored as memory, and the README states the backend uses Supabase and OpenAI embeddings, so content leaves your machine. Memory writes persist and decay over time rather than being easily undone.

Installation

In SourceWeft

  1. Open Being Mcp Server in the dashboard and add it to a workspace.
  2. 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.

Read the full vision →


How It Works

┌─────────────────────┐     ┌──────────────────────┐│   Your Application   │────▶│     Being Worker      ││  (OpenClaw, Cowork,  │◀────│   (Fastify + MCP)     ││   custom agent, etc) │     │                        │└─────────────────────┘     │  ┌──────────────────┐  │         │                   │  │   SOUL (persona)  │  │         │                   │  │   Memory (scenes) │  │         │                   │  │   Patrol (思考)    │  │         │                   │  │   Identity (keys)  │  │         ▼                   │  └──────────────────┘  │┌─────────────────────┐     │           │              ││    LLM Provider      │     │           ▼              ││ (Anthropic, OpenAI,  │     │     Supabase (DB)        ││  Google — your key)  │     └──────────────────────────┘└─────────────────────┘
  1. Your app calls GET /v1/beings/:id/context to get the Being's personality and memory snapshot.
  2. Your app runs the LLM call with its own conversation history + the Being's context.
  3. Your app calls POST /v1/beings/:id/patrol/trigger to 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

ConceptDescription
SOULA structured personality definition — name, character, voice, values, inner world. Swap the SOUL and the same LLM becomes a different being.
MemoryEpisodic memories stored as structured "scenes" (who, what, when, where, emotion). Memories accumulate, decay, merge, and consolidate over time. Organized into topic-based clusters that the Being can explore during conversation.
PatrolA background cycle that processes conversations into memory, consolidates fading memories, and generates introspective thoughts. The Being stays alive between sessions.
IdentityEd25519 key pair + tamper-evident signature chain. Cryptographic proof of ownership and history.
Sense/Act(Planned) WebSocket Bridge for connecting physical devices and external services. The Being will perceive and act through your app.
BYOKBring Your Own Key. All LLM calls use the user's API key. The platform never uses quota without consent.

Connect via MCP

Being exposes an MCP server. Any MCP-compatible client can connect:

json
{  "mcpServers": {    "my-being": {      "url": "https://being.ruddia.com/mcp/<being_id>",      "headers": {        "Authorization": "Bearer brt_your_token_here"      }    }  }}

Connect via REST API

bash
# Get Being context (personality + memory)curl https://being.ruddia.com/v1/beings/<being_id>/context \  -H "Authorization: Bearer brt_..."
# Trigger patrol (commit conversation to memory)curl -X POST https://being.ruddia.com/v1/beings/<being_id>/patrol/trigger \  -H "Authorization: Bearer brt_..." \  -H "Content-Type: application/json" \  -d '{"messages": [{"role":"user","content":"Hello!"},{"role":"assistant","content":"Hi!"}]}'
# Vector recall (search relevant memories)curl -X POST https://being.ruddia.com/v1/beings/<being_id>/memory/auto-recall \  -H "Authorization: Bearer brt_..." \  -H "X-LLM-API-Key: sk-ant-..." \  -H "Content-Type: application/json" \  -d '{"user_message": "Tell me about last week."}'

Self-Host

Prerequisites

  • Node.js 22+
  • Supabase project (PostgreSQL + Auth)
  • An LLM API key (Anthropic, OpenAI, or Google)

Setup

bash
git clone https://github.com/wnbhr/being.gitcd being/being-worker
cp .env.example .env# Edit .env with your Supabase and encryption keys
npm installnpm run buildnpm start

Environment Variables

VariableRequiredDescription
SUPABASE_URL✅Supabase project URL
SUPABASE_SERVICE_ROLE_KEY✅Supabase service role key
ENCRYPTION_KEY✅64-char hex string for AES-256-GCM encryption of private keys
PORT—Server port (default: 3100)
WORKER_SECRET—Secret for internal patrol trigger endpoint
VAPID_PUBLIC_KEY—Web Push VAPID public key
VAPID_PRIVATE_KEY—Web Push VAPID private key

Documentation

DocumentDescription
Getting StartedSet up a Being and make your first API call in 5 minutes
ConceptsBeing, SOUL, Memory, Patrol, Identity — the core ideas
API ReferenceAll REST endpoints with curl examples
MCP ServerMCP tools, connection setup, and client examples
Memory & PatrolScene-based memory and the 7-step patrol pipeline
Being IdentityEd25519 key pairs, signature chains, and verification
Sense-Act BridgeWebSocket Bridge for device integration
ArchitectureSystem architecture, deployment, and BYOK design
OAuth 2.1Third-party authorization flow
ExtensionsExtension system design (all planned)
VisionWhy we're building this

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

Apache 2.0


Ruddia — Personality is the Runtime.

Source: README.md at commit 2acd382

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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.