Skip to main content
SoulForge connects to MCP servers, exposing their tools alongside built-in tools. Three transports are supported: stdio (local subprocess), Streamable HTTP (remote), and SSE (legacy remote).

Quick start

Add a simple stdio server to your config:
Tools from this server are now available as mcp__github__<tool>.

Configuration

Add mcpServers to your global config (~/.soulforge/config.json) or project config (.soulforge/config.json). Project config overrides global by server name.

Config reference

Tool namespacing

MCP tools are namespaced as mcp__<server>__<tool> to prevent collisions with built-in tools. A server named “github” with tool “create_issue” becomes mcp__github__create_issue.

Transport types

stdio — Spawns a local subprocess. The server communicates via JSON-RPC over stdin/stdout. Best for local tools and development. http — Streamable HTTP (recommended for remote servers). Modern MCP transport with efficient streaming. sse — Server-Sent Events. Legacy remote transport. Use http for new servers.

Lifecycle

  • Startup: All enabled servers connect with bounded concurrency (max 5 simultaneous)
  • Retry: Failed servers retry up to 3 times with exponential backoff (1s, 2s, 4s)
  • Auto-restart: Servers that crash automatically restart (stdio transport only)
  • Cleanup: On exit, all connections are closed and subprocesses terminated

TUI shortcuts

Open the MCP manager with /mcp or Ctrl+K → search “mcp”.

Headless mode

MCP servers connect automatically in headless mode. Tools are available to the agent immediately: