1. Context gets too big Teams add more MCP servers and the context grows fast. The model sees too many tools and picks the wrong one. Accuracy drops and workflows break. This blocks adoption because the setup works in demos but fails in real use.

2. Setup does not scale Each MCP server needs its own config, port, and auth. Teams end up running many servers with no shared control. It is hard to track and easy to break. Most teams stop here because it takes too much time to maintain.

3. No enterprise security No SSO. No audit logs. No user rules. Most teams pass around raw tokens. Security teams block the rollout. This stops MCP adoption in companies that care about compliance.

Arka solves these adoption problems with one gateway.

One setup for all MCP servers • One token per user with SSO

• User rules and tool rules

• Tool filtering to keep context small

• Better accuracy with many tools

• Logs for every call

• Open source or cloud

We are also adding:

• Agent access with safe rules

• Workflows you can convert into your own MCP server

Our goal is simple: make MCP adoption possible at scale.

Repo: https://github.com/KenisLabs/arka-mcp-gateway

Cloud: https://www.kenislabs.com

Would love your feedback!