Skip to main content

Deploy with an agent

Copy agent prompt

Before you start

Connect your AWS account and choose a project. Review the upstream deployment instructions for the release you plan to pin.

Data dependencies

No SQL database for the proxy. An upstream MCP server may have its own dependencies.

Deployment order

  1. Prepare one approved MCP tool server first. For remote MCP, confirm that MCPO can reach its authenticated Streamable HTTP or SSE endpoint. For standard input and output, include the tool and its runtime in the same image.
  2. Use ghcr.io/open-webui/mcpo or a GitHub build on port 8000. Supply the upstream URL or command and configure MCPO authentication. Use runtime secret injection for upstream credentials and the proxy key.
  3. Restrict network access and expose only reviewed tools. If any tool requires a database, create and connect it in the upstream server before starting MCPO.
  4. Start the upstream service first if it runs remotely. Start MCPO, check the generated OpenAPI schema for the expected tools, and then connect the consumer.
Use Runtime variables for runtime credentials. For a Spring Winter web server, set an app-supported health path that returns HTTP 200 without credentials. Check History before running the application check.

Verify the deployment

Invoke one harmless tool as an authorized client and verify that an unauthorized request is denied.