u/CampaignFuture5874

The problem I ran into was pretty simple: once you start using multiple MCP servers, the setup gets messy fast. Different tools, different endpoints, different configs, and it becomes annoying to manage.

So I made MCPBox.

What it does right now:

• group MCP servers by project
• expose one MCP endpoint per project
• embedded UI for managing servers
• inspect tools/capabilities visually
• pause / disable servers when needed
• audit/logging support
• supports local STDIO servers and remote HTTP streaming servers

What it is not right now:

• not multi-user
• no auth yet
• not trying to be a full observability platform
• still an early first release

Repo:
GitHub: github.com/ArturSaleev/MCPBox

First release:
github.com/ArturSaleev/MCPBox/releases/tag/v1.0.0

I wrote the first version very recently, so I’d really like feedback on:

• whether the “one endpoint per project” model makes sense
• what’s missing in the UI
• whether auth / permissions should be the next priority
• what kind of MCP workflow this would actually help with in real usage