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 分

    请在仓库或注册中心条目中声明许可证。