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.
We read the source, 4 d ago · rules 995398eba69f
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.
postinstall: node scripts/install.js
const child = spawn(binary, process.argv.slice(2), {
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);
.with_known_hosts_file("/home/devuser/.ssh/known_hosts")
-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.
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.
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.
claude mcp add soma -- npx -y @dinglebear/soma
{
"mcpServers": {
"soma": {
"command": "npx",
"args": [
"-y",
"@dinglebear/soma"
]
}
}
}
[mcp_servers.soma]
command = "npx"
args = ["-y", "@dinglebear/soma"]
{
"mcpServers": {
"soma": {
"command": "npx",
"args": [
"-y",
"@dinglebear/soma"
]
}
}
}
{
"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).
Android device automation for AI agents: MCP server, CLI, and plugin runtime over adb.
JSON-first Coreutils CLI for AI agents. 114 commands with sandbox, dry-run, and MCP support.
SEAM: local-first memory runtime for AI agents, with retrieval and glassbox provenance over MCP.
Goal and task planning MCP for Codex and AI agents, with evidence-backed completion.
Self-hosted MCP memory for AI agents: persistent context with evidence-backed claims.
Evidence-backed web research for AI agents with citations and confidence scores.
AI Agents Framework with Self Reflection and MCP support
Manifest-driven MCP server scaffolder and runtime hub for tool integrations.
Answers built from our own checks of this server.