Skip to content

    Operations tools for
    your coding agent.

    Monk is the operator for the software your agents write. Your coding agent writes it; Monk ships it and keeps it running — on your cloud, on your bill.

    Monk is a plugin with a local MCP companion. It connects the coding agent to the orchestrator that manages your app and infrastructure.

    Install the plugin.

    You need a supported host, a Monk account, access to the repository and credentials for your target cloud. Complete installation and restart or reload the host before the first request.

    1. 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.

    2. Codex

      Add the marketplace

      codex marketplace add monk-io/monk-plugin

      Run this in a terminal, restart Codex, then open /plugins and install Monk from Monk Plugins.

    3. Cursor

      Open in Cursor marketplace

      Monk is in the Cursor marketplace — install it there.

    Complete the plugin’s browser authentication when prompted. Host-specific setup and authentication.

    A useful first request.

    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.

    For an existing app, use the separate-environment workflow. Keep credentials in the local credential form, not in chat.

    Capabilities and limits.

    What is Monk?

    Monk is an operations agent used through a coding-agent plugin and local MCP companion. It analyzes repositories, prepares deployment plans, connects services and operates workloads in the customer’s cloud account.

    What runs automatically?

    The orchestrator automatically recovers workloads within configured policies. Watcher adds AI diagnosis; its proposed fixes need your approval.

    What needs human input?

    Supply provider credentials and secrets through the local companion’s forms. Review deployment plans, resource changes, warnings and costs before provisioning. Watcher’s proposed AI remediation requires approval.

    How does existing-app adoption work?

    Monk builds fresh infrastructure from your codebase. Your existing deployment stays untouched. Test the new environment before you switch. Source code does not reproduce production data or undocumented account settings. Data transfer and traffic cutover are separate steps.

    What should an agent do when setup is incomplete?

    Identify missing authentication, team or environment context, credentials, unsupported dependencies and unresolved approvals. Let the user resolve them before requesting deployment. Check operation status before retrying a failed action.

    Where are setup and pricing defined?

    Use the plugin repository for complete host installation and authentication instructions. Check the pricing page and the account’s subscription for applicable terms; proposed capacity pricing is not yet the checkout catalog.