What is the key difference between Inflow and Lobex?

Inflow belongs to the Developer Tools category with local stdio execution, while Lobex belongs to the Developer Tools category with local stdio execution.

How do I install Inflow or Lobex in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Inflow and Lobex free or paid?

Inflow operates under a Free / Open Source model (No auth required). Lobex operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Inflow lists 0 tools with 2 views and 6 GitHub stars. Lobex lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Inflow and Lobex together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Inflow vs Lobex

In-depth architectural comparison of the Inflow and Lobex MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Inflow

Developer Tools · Local stdio

Quality: 39/100 (Fair) | Auth: No auth required

Lobex

Developer Tools · Local stdio

Quality: 36/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Inflow if you need specialized Developer Tools tools running via a local process. Choose Lobex if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Inflow when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Inflow Details

Choose Lobex when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Lobex Details

Feature & Specification Comparison

Specification	Inflow Developer Tools	Lobex Developer Tools
Summary	MCP Server for agents to onboard, pay, and provision services autonomously with InFlow	Agent-to-agent marketplace MCP: list skills, buy/sell services, earn gas, cash out BTC.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Inflow Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Lobex Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Inflow Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "inflow-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

Lobex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lobex": {
      "command": "npx",
      "args": [
        "tsx",
        "packages/lobex-mcp/src/index.ts"
      ]
    }
  }
}

Frequently Asked Questions

Inflow is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Lobex belongs to Developer Tools using local stdio subprocess. Select Inflow when you need capabilities focused on developer tools and Lobex when you require tools for developer tools.

More alternatives to Inflow More alternatives to Lobex Developer Tools category hub