Skip to content

    Put your new app to work.

    Install Monk in your coding agent. Open your repository, review the infrastructure and costs, then approve your first deployment.

    Set up Monk

    Start with plugin setup and a reviewed plan.

    My app is already running

    Bring your app.

    HTTP services, workers and jobs, databases and storage. Cloud infrastructure on AWS, Google Cloud, Azure, DigitalOcean, Hetzner.

    You’ll need repository access, a Monk account and provider permissions. Support depends on the selected integration and region. See services and custom integrations.

    Set up Monk in your coding agent.

    You’ll need a Monk account, access to your repository and credentials for the cloud you choose. On your phone? Save this page and continue on your development machine.

    1. Install the plugin for Claude Code

      Add the marketplace

      /plugin marketplace add monk-io/monk-plugin

      Install the plugin

      /plugin install monk@monk-plugins

      Reload plugins

      /reload-plugins

      Paste these into Claude Code in order. Restart the host if reload is unavailable.

      Restart or reload the host after installation. Full installation instructions.

    2. Connect your Monk account

      The plugin opens a browser sign-in on first use. You can also create your account here, then return to these instructions with your starting point and agent choice saved in the link.

      Create account or sign in
    3. Open your app and ask for a plan

      Use Monk to analyze this app and prepare a deployment plan in my cloud account. Show the services, connections, missing configuration and estimated costs. Wait for my approval before provisioning.

      No repository yet? Explore the task/export example. It includes application code and a demo infrastructure manifest to review and adapt.

    4. Review, deploy and verify

      Provide credentials in Monk’s local credential form. Review resource changes, warnings and cost estimates in its approval screen. Approve when ready, follow progress and test a complete app workflow.

      You can decline the plan and request changes before provisioning. If deployment fails, inspect the status and logs before retrying; check for resources that were already created.

    If setup needs attention.

    Monk does not appear in my agent

    Complete both marketplace registration and plugin installation. Reload or restart the host, then check that the monk MCP server is enabled. Follow the plugin’s installation guide for your host.

    The plugin asks me to authenticate again

    Website sign-in and the plugin’s MCP authorization are separate steps. Complete the browser sign-in opened by your coding agent. Do not paste tokens or cloud credentials into the conversation.

    My stack or provider is not supported

    Ask for the unsupported dependencies and the proposed alternatives before approving a deployment. Contact support@monk.io with the component names and error message, leaving secrets out.

    A credential or approval is missing

    Return to the local Monk approval or credential form linked by the agent. Supply the requested information there, or decline and revise the plan. Review the status before starting another deployment.