slife-mcp 0.1.1

Standalone MCP proxy service — manages persistent connections to external MCP servers

slife-mcp

Standalone MCP proxy service — manages persistent connections to external MCP servers and exposes them through a single MCP endpoint.

Quick Start

pip install slife-mcp

# Run — auto-detects mode:
slife-mcp                      # with slife.json5 → HTTP, without → stdio
slife-mcp --port 8888          # HTTP on custom port

How It Works

MCP clients ←→ slife-mcp ←→ external MCP servers (filesystem, search, ...)

slife-mcp maintains persistent connections to external MCP servers. Clients connect to slife-mcp and get access to all tools from all connected servers through a single endpoint.

Configuration

Create slife.json5 in your working directory:

{
  mcp: {
    // wrapper.url — where clients connect to slife-mcp
    wrapper: {
      url: "http://127.0.0.1:9876/mcp",
    },

    // External MCP servers to auto-connect at startup
    servers: {
      filesystem: {
        command: "npx",
        args: ["-y", "@modelcontextprotocol/server-filesystem", "/allowed/path"],
      },
      serper: {
        command: "npx",
        args: ["-y", "serper-search-scrape-mcp-server"],
        env: {
          SERPER_API_KEY: "${SERPER_API_KEY}",
        },
      },
    },
  },
}

Management Tools

Once running, clients can call these tools to manage connections:

Tool	Description
mcp_add_server	Add and connect to an external MCP server at runtime
mcp_remove_server	Disconnect and remove a server
mcp_list_servers	List all configured servers with status
mcp_list_tools	List all tools from connected servers
mcp_call_tool	Call a tool on a connected server
mcp_reload	Reconnect to refresh tool lists

Transport Modes

Mode	Trigger	Use case
HTTP	TTY (terminal)	Standalone service, shared by multiple clients
stdio	Piped stdin	Child process, used by slife agent

HTTP mode is auto-detected when run from a terminal with slife.json5 present. stdio mode is used when spawned as a child process.

License

MIT