Being MCP Server

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

Local serverstdioTypeScript

What is the Being MCP server?

Being MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Personality Runtime for AI agents — persistent memory, personality, and relationships via MCP.

What you get

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.

Setting it up

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Being is connected, these are the calls the assistant has available:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — The Setup tool exposed by this server

Configuration and credentials

You will need 6 environment variables: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, ENCRYPTION_KEY, WORKER_SECRET, VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the being mcp server does with a few real requests.

Choosing this one

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Being's toolset — Prerequisites, Setup — is a fair guide to whether it matches your workflow. It is maintained by com.ruddia; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Being's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
SetupThe Setup tool exposed by this server.

How to install the Being MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 22+ - Supabase project (PostgreSQL + Auth) - An LLM API key (Anthropic, OpenAI, or Google)
VariableDescriptionRequired
SUPABASE_URLEndpoint or connection string the server talks to.Yes
SUPABASE_SERVICE_ROLE_KEYCredential the server authenticates with.Yes
ENCRYPTION_KEYCredential the server authenticates with.Yes
WORKER_SECRETCredential the server authenticates with.Yes
VAPID_PUBLIC_KEYCredential the server authenticates with.Yes
VAPID_PRIVATE_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Being to Prerequisites.
  • Use Being to Setup.

Frequently asked questions

It connects Being to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Prerequisites, Setup) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Being directly.