Developer · Local MCP server
Soma
RMCP runtime for provider-backed agents with CLI, REST, HTTP MCP, plugins, and scaffold support.
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
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | ghcr.io/dinglebear-ai/soma:0.10.0 | — | stdio |
| npmruntime: npx | @dinglebear/soma | 0.10.0 | stdio |
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
| Server | Runs |
|---|---|
| Arcane RMCPArcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP. | Local · stdio |
| Cortex RMCPSelf-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. | Local · stdio |
| Cortex RMCPRust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation. | Local · stdio |
| Gotify RMCPRust MCP server and CLI for Gotify push notifications and message management. | Local · stdio |
| Gotify RMCPGotify notifications and app, client, and message management over MCP and CLI. | Local · stdio |
| LabbyRust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI. | Local · stdio |
| Synapse RMCPHost, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI. | Local · stdio |
| Synapse RMCPRust MCP and CLI server for Docker, host inspection, SSH, logs, ZFS, and safe file operations. | Local · stdio |
| Tailscale RMCPTailscale device, route, DNS, key, user, and ACL management over MCP and CLI. | Remote & Local · HTTP, stdio |
| Tailscale RMCPRust MCP server and CLI for Tailscale devices, users, keys, policies, and auth. | Local · stdio |
| UniFi RMCPRust MCP server and CLI for UniFi Network controller operations. | Local · stdio |
| UniFi RMCPRust MCP server and CLI for UniFi Network controller operations. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| SolidPingSelf-hostable uptime monitoring: create checks, read incidents, manage status pages. | Remote · HTTP |
| Solitaire for AgentsIdentity infrastructure for AI agents. Evolving persona, session continuity, self-tuning retrieval. | Local · stdio |
| SolumbeDeterministic local repository context, impact analysis, and merge-readiness evidence for AI agents. | Local · stdio |
| 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 · HTTP |
| SomaExecution-verified code generation and verification with signed, offline-checkable certificates. | Local · stdio |
| Sonar MCP ServerRead-only SonarQube Community Build access for AI agents: issues, hotspots, rules, code snippets. | Local · stdio |
| SonarQube MCP ServerAnalyze code quality and security with SonarQube Server or Cloud directly in AI assistants. | Local · stdio |
| SondeLocal code graph for TypeScript, Python and Swift: who calls this, what breaks if I change it. | Local · stdio |