Back to Browse

Being MCP Server

by Wnbhr
Developer ToolsLow Risk9.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Personality Runtime for AI agents — persistent memory, personality, and relationships via MCP

About

Personality Runtime for AI agents — persistent memory, personality, and relationships via MCP

Security Report

9.7
Low Risk9.7Low Risk

Valid MCP server (5 strong, 6 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

8 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Being Worker base URLOptional

Environment variable: BEING_API_URL

Auth token (brt_...)Required

Environment variable: BEING_API_TOKEN

Target Being IDOptional

Environment variable: BEING_ID

Anthropic API key for trigger_patrol (BYOK)Required

Environment variable: LLM_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-ruddia-being-mcp-server": {
      "env": {
        "BEING_ID": "your-being-id-here",
        "LLM_API_KEY": "your-llm-api-key-here",
        "BEING_API_URL": "your-being-api-url-here",
        "BEING_API_TOKEN": "your-being-api-token-here"
      },
      "args": [
        "-y",
        "@ruddia/being-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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:

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

Connect via REST API

# 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

git clone https://github.com/wnbhr/being.git
cd being/being-worker

cp .env.example .env
# Edit .env with your Supabase and encryption keys

npm install
npm run build
npm start

Environment Variables

VariableRequiredDescription
SUPABASE_URLSupabase project URL
SUPABASE_SERVICE_ROLE_KEYSupabase service role key
ENCRYPTION_KEY64-char hex string for AES-256-GCM encryption of private keys
PORTServer port (default: 3100)
WORKER_SECRETSecret for internal patrol trigger endpoint
VAPID_PUBLIC_KEYWeb Push VAPID public key
VAPID_PRIVATE_KEYWeb 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.

Reviews

No reviews yet

Be the first to review this server!