Developer · Local MCP server

Soma

RMCP runtime for provider-backed agents with CLI, REST, HTTP MCP, plugins, and scaffold support.

Visit Soma's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
ai.dinglebear/soma
Version
0.10.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
OCI image (Docker), npm
Published
2026-08-05
Updated
2026-08-05
Publisher
ai.dinglebear · 22 servers with pages here
Website
soma.dinglebear.ai
Repository
github.com/dinglebear-ai/soma
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
OCI image (Docker)runtime: dockerghcr.io/dinglebear-ai/soma:0.10.0—stdioSOMA_HOME, SOMA_PROVIDER_DIR, SOMA_API_URL, SOMA_API_KEY (secret), RUST_LOG
npmruntime: npx@dinglebear/soma0.10.0stdioSOMA_HOME, SOMA_PROVIDER_DIR, SOMA_API_URL, SOMA_API_KEY (secret), RUST_LOG

How to connect Soma

Soma runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/dinglebear-ai/soma:0.10.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e SOMA_HOME -e SOMA_PROVIDER_DIR -e SOMA_API_URL -e SOMA_API_KEY -e RUST_LOG ghcr.io/dinglebear-ai/soma:0.10.0. It reads these environment variables: SOMA_HOME, SOMA_PROVIDER_DIR, SOMA_API_URL, SOMA_API_KEY (secret) and RUST_LOG; set them in the client's configuration for this server.

Soma runs locally from a Node.js package published to the npm registry: @dinglebear/soma version 0.10.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @dinglebear/soma@0.10.0. It reads these environment variables: SOMA_HOME, SOMA_PROVIDER_DIR, SOMA_API_URL, SOMA_API_KEY (secret) and RUST_LOG; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "soma": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SOMA_HOME",
        "-e",
        "SOMA_PROVIDER_DIR",
        "-e",
        "SOMA_API_URL",
        "-e",
        "SOMA_API_KEY",
        "-e",
        "RUST_LOG",
        "ghcr.io/dinglebear-ai/soma:0.10.0"
      ],
      "env": {
        "SOMA_HOME": "<value>",
        "SOMA_PROVIDER_DIR": "<value>",
        "SOMA_API_URL": "<value>",
        "SOMA_API_KEY": "<secret>",
        "RUST_LOG": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from ai.dinglebear

All 22 →
ServerRunsEndpoint or package
Arcane RMCPArcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP.Local · stdionpm: @dinglebear/rarcane
Cortex RMCPSelf-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.Local · stdionpm: @dinglebear/cortex
Cortex RMCPRust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.Local · stdionpm: cortex-rmcp
Gotify RMCPRust MCP server and CLI for Gotify push notifications and message management.Local · stdionpm: gotify-rmcp
Gotify RMCPGotify notifications and app, client, and message management over MCP and CLI.Local · stdionpm: @dinglebear/rgotify
LabbyRust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.Local · stdionpm: @dinglebear/labby
Synapse RMCPHost, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI.Local · stdionpm: @dinglebear/synapse
Synapse RMCPRust MCP and CLI server for Docker, host inspection, SSH, logs, ZFS, and safe file operations.Local · stdionpm: synapse-rmcp
Tailscale RMCPTailscale device, route, DNS, key, user, and ACL management over MCP and CLI.Remote & Local · HTTP, stdiots.dinglebear.ai
Tailscale RMCPRust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.Local · stdionpm: tailscale-rmcp
UniFi RMCPRust MCP server and CLI for UniFi Network controller operations.Local · stdionpm: @dinglebear/runifi
UniFi RMCPRust MCP server and CLI for UniFi Network controller operations.Local · stdionpm: unifi-rmcp

More developer servers

All 6,250 →
ServerRunsEndpoint or package
SolidPingSelf-hostable uptime monitoring: create checks, read incidents, manage status pages.Remote · HTTPsolidping.io
Solitaire for AgentsIdentity infrastructure for AI agents. Evolving persona, session continuity, self-tuning retrieval.Local · stdioPyPI: solitaire-ai
SolumbeDeterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.Local · stdionpm: @bashbop/solumbe
Solvicus FinOps - GCP Committed Use Discount (CUD) OptimizationFinOps for Google Cloud: size 1- and 3-year CUD commitments to known demand. Also solves LP/MIP.Remote · HTTPmcp.solvicus.com
SomaExecution-verified code generation and verification with signed, offline-checkable certificates.Local · stdionpm: soma-verify-mcp
Sonar MCP ServerRead-only SonarQube Community Build access for AI agents: issues, hotspots, rules, code snippets.Local · stdioOCI image (Docker): ghcr.io/igorolv/sonar-mcp-server:0.1.0
SonarQube MCP ServerAnalyze code quality and security with SonarQube Server or Cloud directly in AI assistants.Local · stdioOCI image (Docker): docker.io/sonarsource/sonarqube-mcp
SondeLocal code graph for TypeScript, Python and Swift: who calls this, what breaks if I change it.Local · stdionpm: @cheppulabs/sonde