Skip to main content
Monk installs as a plugin directly into your coding agent. One install gets you everything: the plugin sets up a local monk-agent companion, connects your agent to it over MCP, and loads the monk skill. There is no separate app to run and nothing to configure by hand.
The plugin installs monk-agent under ~/.monk/bin and connects your agent to its MCP endpoint on 127.0.0.1:7419. On first use it also installs the Monk CLI and daemon through your system package manager. Your agent asks for approval before privileged operations, and your cloud credentials are never exposed to the agent.

​
Requirements

  • Claude Code, Cursor, OpenAI Codex, or Google Antigravity.
  • Network access to GitHub and https://get.monk.io/stable so the plugin can download the signed monk-agent archive.
  • Permission to run a local helper process on loopback, normally 127.0.0.1:7419.
The plugin installs monk-agent under your user profile:

​
Claude Code

Run these commands inside Claude Code:
Then reload the current session:
After reload, run /mcp — Monk should appear as an MCP server. If Claude Code asks you to authenticate, complete the browser sign-in flow from /mcp.

​
Cursor

Monk is listed in the Cursor marketplace, so you can install it either way:
  • From chat: run this command in Cursor chat:
  • From the UI: open Cursor’s Customize tab, find Monk under plugins (or start from the marketplace listing), and click install.
Restart Cursor after installation, then open Settings → Tools & MCP and confirm Monk is listed and enabled. If Cursor reports that Monk needs login, use Cursor’s MCP login flow for the monk server.
/add-plugin https://github.com/monk-io/monk-plugin also works if you prefer installing straight from the GitHub repository.

​
Codex

Add the Monk marketplace from your terminal:
Start Codex in the project where you want to use Monk, then open the plugin browser:
In the plugin browser, open the monk-plugins marketplace and install Monk. Restart Codex afterward so the Monk skill and MCP config are loaded, then verify with /mcp. If Codex reports that Monk needs authentication, run:
Complete the browser sign-in flow, then return to Codex and run /mcp again.
The tested Codex CLI command is codex marketplace add monk-io/monk-plugin. Do not use codex plugin marketplace add; that is not the Codex CLI marketplace command.

​
Antigravity

Antigravity 2.0 (the standalone desktop app and CLI) uses a plugin directory instead of a marketplace command:
The start script launches monk-agent in the background and writes a monk entry to ~/.gemini/config/mcp_config.json. Open a project in Antigravity afterward — plugins load in workspace context, so the monk skill and MCP tools become available once a project is open.

​
Sign In

After installing on any agent, ask it to check that everything is ready:
Monk inspects the local runtime, installs anything that is still missing, and walks you through the browser sign-in. Signing up starts a free trial — no credit card required.

​
What the Plugin Sets Up

1

The host loads the Monk skill and plugin manifest

Your coding agent reads the plugin metadata and makes Monk available.
2

The plugin starts monk-agent

The bundled launcher installs monk-agent if it is missing, starts it locally, and waits for the MCP endpoint.
3

monk-agent checks runtime state

The local agent verifies the Monk CLI, daemon, auth, and workspace state. If setup is needed, it opens the sign-in or setup flow.
4

Your coding agent connects over MCP

The agent talks to Monk at http://127.0.0.1:7419/mcp. Privileged operations still go through Monk approval flows.
Your coding agent should call Monk MCP tools for infrastructure and runtime operations — not run direct monk ... shell commands against live Monk-managed infrastructure.
Any other MCP-capable agent can connect to the local monk-agent endpoint at http://127.0.0.1:7419/mcp once it is installed and running, but the plugin hosts above are the supported, tested paths.

​
Updating

​
Uninstall

First remove the plugin from the host: Host uninstall removes the plugin, but not the local companion. To remove it, run the cleanup script from the plugin repository:
On Windows:
To also remove the Monk runtime components (CLI and daemon), add the runtime option: --runtime on macOS/Linux, -Runtime on Windows.

​
Troubleshooting

Monk does not show up in the agent
  • Reload or restart the agent after installation.
  • Claude Code: run /reload-plugins, then /mcp.
  • Cursor: open Settings → Tools & MCP and confirm Monk is enabled.
  • Codex: run /plugins and confirm Monk is installed from monk-plugins.
  • Antigravity: confirm ~/.monk/bin/monk-agent status reports running and that ~/.gemini/config/mcp_config.json has a monk entry.
The MCP server is missing or offline
  • Confirm no other process is blocking 127.0.0.1:7419.
  • Restart the agent so the bundled launcher can start monk-agent again.
Authentication is required
  • Claude Code: run /mcp and use the MCP authentication prompt.
  • Cursor: use Cursor’s MCP login flow for the monk server.
  • Codex: run codex mcp login monk.
The plugin installed but Monk runtime setup is incomplete Ask your coding agent:
Monk will inspect the local runtime, open any required sign-in or setup flow, and continue after checks pass.

More troubleshooting

Common setup and connection issues

​
Next Steps

First deployment

Deploy your first application in minutes

Connect your cloud

Credentials and permissions for every provider