Tools / Gateway

Obot

Gateway

Open-source MCP gateway with policy enforcement and audit logging.

What it solves

Teams adopting MCP end up with servers registered in every developer's local client config, with no central record of which servers exist or who can use them. Obot gives you one self-hosted gateway where MCP servers are registered, permissioned, and audited.

How it works

You run Obot inside your own infrastructure and register MCP servers with it. Users and agents connect through the gateway, which enforces access policies and records tool calls, giving you an audit trail that local client configs cannot provide.

Pros & cons

Pros

Open source and self-hosted — no data leaves your environment.
Central registry turns scattered MCP configs into a governed catalog.
Audit logging of tool calls out of the box.

Considerations

You own the uptime, upgrades, and hardening of the gateway itself.
Younger project than incumbent API gateways — expect a moving feature set.
Enterprise support pricing is not public.

When to choose it

Choose Obot when you want an open-source, self-hosted control point for MCP and your team is comfortable operating its own infrastructure.

Disclaimer: Tool capabilities and pricing change. Verify current details on the vendor's official website before making procurement decisions.