Being Mcp Server

com.ruddia由 ruddia.com 發布v1.0.0更新於 Oct 24, 2026

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

已驗證STDIO僅桌面知識與記憶AI 與機器學習

概覽

AI 產生的概覽

本機 MCP 伺服器,將助理連接到 Being Worker,為 AI 提供持久人格、情境記憶與身分。

可以做什麼
取得某個 Being 的人格與記憶脈絡,讓助理在對話中維持一致人設並回憶過往場景。透過觸發背景 patrol 循環把對話提交回 Being 的記憶,該循環會整合、衰減記憶並產生內省想法。依與目前訊息的相關度檢索 Being 已儲存的記憶。README 也記錄了提供相同脈絡、patrol 與回憶操作的 REST API,以及以 Ed25519 金鑰對和簽章鏈為基礎的加密身分。
適用情境
當你希望助理跨工作階段維持穩定人設與長期記憶,而不是每次都從無狀態模型重新開始時使用。適合陪伴型代理、角色扮演或角色驅動應用,以及持久化代理記憶的實驗。
執行需求
以本機 npm 套件透過 stdio 執行。需要 Being Worker 基礎位址(BEING_API_URL)、目標 Being ID(BEING_ID)與 Being 驗證權杖(BEING_API_TOKEN)。觸發 patrol 需要 Anthropic API 金鑰(LLM_API_KEY),費用計入你自己的金鑰。需要能存取 Being Worker 的網路。
安裝前請注意
需要祕密驗證權杖與 LLM API 金鑰;LLM 金鑰用於你自己的帳戶,觸發 patrol 可能產生供應商費用。對話會傳送到 Being Worker 並存為記憶,README 說明後端使用 Supabase 與 OpenAI 嵌入,因此內容會離開你的機器。記憶寫入會持久保存並隨時間衰減,不易復原。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Being Mcp Server,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源:README.md,提交 2acd382

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。