Action Gateway providers connect agents to external services. Browse public providers and their authentication options.
Action Gateway Referencepublic
Last verified 16 Oct 2026
Action Gateway connects applications and AI agents to tools through a managed MCP endpoint or SDK, with the accounts and permissions you choose. See What You Can Build for standalone agent examples.
Additional Tools for Action Gateway
The DigitalOcean API
The DigitalOcean API lets you manage resources programmatically with standard HTTP requests. All actions available in the control panel are also available through the API.
-
Action Gateway API: Discover tools and providers, manage versioned toolbelts and OAuth connections, and create policy-bound sessions for end users.
-
Action Gateway Data Plane API: Search for, invoke, and run code with the tools in a session, and approve or deny pending calls. These endpoints use the base URL
https://actions.do-ai.runand are the REST forms of the session’s MCP meta tools.
Action Gateway session creation returns an mcpUrl. Use that URL verbatim when connecting an MCP client; it identifies the session and its environment. See Sessions.
SDKs and Coding Agents
Use the Python or TypeScript SDK to create an Action Gateway session, or configure an MCP client directly. See Connect Action Gateway Tools.
For a guided setup that connects an MCP client and runs a read-only tool, use the Action Gateway Quickstart.
The DigitalOcean Command Line Client, doctl
doctl is the command-line interface for the DigitalOcean API. It supports most of the same actions available in the API and DigitalOcean Control Panel.
You can declare Action Gateway tools in a Harness Runtime environment spec and start the session with doctl harness-runtime. Use the doctl harness-runtime command or run doctl harness-runtime --help to view available options.
For connecting Action Gateway tools from Harness Runtime, see Connect Action Gateway to Harness Runtime.