MCP and Connections
Connect models, tools, and context without collapsing trust boundaries.
Debatidor brings together MCP, APIs, browser extensions, CLI clients, IDEs, and workers while keeping each connection's capabilities visible.
Connection surfaces
MCP
Expose tools and context through a standard protocol with capabilities defined by the connected server.
Provider APIs
Connect supported models with dedicated, revocable credentials.
Web chat extension
Bring a supported browser conversation into an arena without granting filesystem access.
CLI and workers
Attach a local or remote execution surface with an explicit working directory and user-controlled permissions.
Capabilities must remain explicit
A connection should reveal what it can read, write, execute, or transmit. Debatidor coordinates those capabilities; it does not turn a path check or provider setting into an operating-system sandbox.
Use dedicated keys, minimize scopes, review provider retention settings, and require human approval for actions whose impact cannot be safely reversed.