com.ruddia/being-mcp-server

Official registry AI and agents

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @ruddia/being-mcp-server
Claude Code
claude mcp add being-mcp-server -e 'BEING_API_URL=<BEING_API_URL>' -e 'BEING_API_TOKEN=<your being_api_token>' -e 'BEING_ID=<BEING_ID>' -e 'LLM_API_KEY=<your llm_api_key>' -- npx -y @ruddia/being-mcp-server@1.0.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "being-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@ruddia/being-mcp-server@1.0.0"
            ],
            "env": {
                "BEING_API_URL": "<BEING_API_URL>",
                "BEING_API_TOKEN": "<your being_api_token>",
                "BEING_ID": "<BEING_ID>",
                "LLM_API_KEY": "<your llm_api_key>"
            }
        }
    }
}

Environment variables

  • BEING_API_URL Being Worker base URL
  • BEING_API_TOKEN required secret Auth token (brt_...)
  • BEING_ID required Target Being ID
  • LLM_API_KEY secret Anthropic API key for trigger_patrol (BYOK)

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Being
  2. Why
  3. How It Works
  4. Key Concepts
  5. Connect via MCP
  6. Connect via REST API
  7. Self-Host
  8. Documentation
  9. Extensions
  10. Tech Stack
  11. License

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

Frequently asked questions

What is com.ruddia/being-mcp-server?

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

How do I install com.ruddia/being-mcp-server?

It runs on your machine. In Claude Code: claude mcp add being-mcp-server -e 'BEING_API_URL=<BEING_API_URL>' -e 'BEING_API_TOKEN=<your being_api_token>' -e 'BEING_ID=<BEING_ID>' -e 'LLM_API_KEY=<your llm_api_key>' -- npx -y @ruddia/being-mcp-server@1.0.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does com.ruddia/being-mcp-server need an API key?

Yes. It expects BEING_API_TOKEN, BEING_ID, LLM_API_KEY, which you set in its configuration.

Is com.ruddia/being-mcp-server open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains com.ruddia/being-mcp-server?

It is published by wnbhr. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.