mcpdirectory.dev
9,129 servers · updated 23 Sept

Soma MCP server

community Active last commit 16 d 
{
  "mcpServers": {
    "dinglebear-soma": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/dinglebear-ai/soma:0.10.0"
      ],
      "env": {
        "SOMA_MCP_TOKEN": "<soma_mcp_token>",
        "SOMA_API_URL": "https://...",
        "SOMA_API_KEY": "<soma_api_key>",
        "SOMA_MCP_PUBLIC_URL": "https://...",
        "SOMA_MCP_GOOGLE_CLIENT_ID": "<soma_mcp_google_client_id>",
        "SOMA_MCP_GOOGLE_CLIENT_SECRET": "<soma_mcp_google_client_secret>"
      }
    }
  }
}
file .mcp.json (in your project root)version 0.10.0

What it does

Soma is an RMCP runtime that serves agent capabilities through MCP, CLI, REST, and HTTP interfaces. It loads provider definitions from files or Rust code and exposes them across multiple transport layers with built-in auth, validation, and observability.

  • Load provider capabilities from JSON, TypeScript, Python, WebAssembly, or Markdown files and expose them as MCP tools, CLI commands, and REST routes.
  • Run a single MCP tool that dispatches to multiple providers, keeping tool lists compact while maintaining full capability discovery.
  • Deploy a pre-built agent runtime with authentication, destructive-action confirmation, logging, and metrics without writing custom Rust code.

Tools this server exposes

ToolDoes
somaSingle MCP tool that dispatches actions to loaded providers using action payloads.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.