mcpbeat Sign in

Soma MCP Server

local only

Soma runs on your own machine — the client starts it, so there is no endpoint to ping. 108 installs a week from npm. Last commit 28 Sep 2026.

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

Installs per day peak 29 · avg 9 · +227% w/w
a month agotoday
108
Installs / week
npm · @dinglebear/soma
1
Stars
13 open issues
28 Sep 2026
Last commit
1 release in 90 days
MIT
License
Rust

What the code does

We read the source, 4 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node scripts/install.js
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    if std::path::Path::new("/.dockerenv").exists()
  return path.join(repoRoot, "target", "debug", binaryName);
            -v /var/run/docker.sock:/var/run/docker.sock \

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add soma -- npx -y @dinglebear/soma
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "soma": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/soma"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.soma]
command = "npx"
args = ["-y", "@dinglebear/soma"]
.cursor/mcp.json
{
  "mcpServers": {
    "soma": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/soma"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "soma": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/soma"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: SOMA_HOME (Host data directory used by the local Soma CLI and stdio MCP runtime), SOMA_PROVIDER_DIR (Host directory scanned for drop-in provider manifests and modules), SOMA_API_URL (Optional deployed platform API or upstream API base URL used by the SomaClient compatibility layer. Leave unset for local provider/runtime mode), SOMA_API_KEY (Optional bearer token or upstream API key for provider-backed calls that use SomaClient. Keep secret), RUST_LOG (Rust tracing filter for local CLI and stdio MCP logs).

Alternatives to Soma

same job, measured the same way
Mobile Agent Harness
by aelindra

Android device automation for AI agents: MCP server, CLI, and plugin runtime over adb.

local only
Aicoreutils
by caseshy

JSON-first Coreutils CLI for AI agents. 114 commands with sandbox, dry-run, and MCP support.

113 installs/wk local only
Seam Runtime
by blackhatshiftey

SEAM: local-first memory runtime for AI agents, with retrieval and glassbox provenance over MCP.

34 installs/wk local only
Planner MCP — provable "done" for AI agents
by monopoly-gold-planner

Goal and task planning MCP for Codex and AI agents, with evidence-backed completion.

43 tools answering
Provena Agent Memory
by admiralpunk

Self-hosted MCP memory for AI agents: persistent context with evidence-backed claims.

242 installs/wk local only
LastSearch
by lastsearch-hq

Evidence-backed web research for AI agents with citations and confidence scores.

569 installs/wk local only
PraisonAI
by mervinpraison

AI Agents Framework with Self Reflection and MCP support

34 002 installs/wk local only
MCP Factory
by jaimenbell

Manifest-driven MCP server scaffolder and runtime hub for tool integrations.

145 installs/wk local only

Soma — questions

Answers built from our own checks of this server.

Why is there no uptime for Soma?
Soma runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @dinglebear/soma was installed 108 times last week.
How do I connect Soma?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @dinglebear/soma straight from npm; nothing to host, nothing to sign up for.
How many people use Soma?
The npm package @dinglebear/soma was installed 108 times in the last week. Week over week that is +227%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Soma open source?
Yes — it is published under the MIT licence, written in Rust, 1 stars on GitHub and 13 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.