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.

This supports any MCP-compatible server, including:

• Pre-built MCP servers — filesystem, web search (Serper, Tavily), fetch, etc.
• REST API servers — anyapi-mcp-server converts OpenAPI specs to MCP tools, making any REST API (GitHub, Jira, GitLab, Slack…) callable as tools.

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:

Transport Modes

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