Skip to main content

​
How This Setup Works

Claude Code does not run the Monk extension itself. The setup has two parts:
  1. Keep Monk running in a supported IDE with MCP enabled for the project
  2. Open Claude Code in the same project so it can use the local-scoped Monk entry that Monk generated

​
Step 1: Enable Monk MCP on the Monk Side

Monk MCP is not enabled by default. Before you open Claude Code, make sure Monk is already running in VS Code, Cursor, Windsurf, or Antigravity with the same project open. Make sure:
  • Monk is installed in one supported IDE that is currently running
  • the project is open in that IDE
  • you ran Monk: Manage MCP Server
  • you chose Enable MCP server
If you are choosing targets manually, include Claude Code for this workspace. Monk writes a local-scoped Claude Code entry in ~/.claude.json under the current project’s path. Read more: Install Monk, MCP Getting Started

​
Step 2: Let Claude Code See Monk

Claude Code supports local-scoped MCP servers stored in ~/.claude.json under the current project’s path. Monk writes that local-scoped project entry for you, so Claude Code needs to be opened in the same project for Monk to become available. Claude MCP Enablement

​
Step 3: Verify Monk from Claude Code

Inside Claude Code, run: 
/mcp
Claude Code’s MCP docs use /mcp to inspect connected servers and their status. You should see Monk listed for the current project.

​
Step 4: Approve or Use Monk

Once Monk is listed, Claude Code can use Monk’s tools when relevant. If Claude Code asks you to authorize, authenticate, or confirm the server from the /mcp flow, approve Monk for this project. You can also type / in Claude Code to see available slash commands, including MCP-provided prompts when a server exposes them. Read more: Claude Code MCP docs

​
What to Ask First

Claude communication with monk Good first requests are:
  • use Monk to analyze this project
  • use Monk to deploy this application
  • ask Monk what services this project needs
  • use Monk to inspect logs for the running backend

​
If Monk Does Not Appear

  • confirm Monk is running in VS Code, Cursor, Windsurf, or Antigravity
  • confirm Monk MCP is enabled there for this workspace
  • confirm that supported IDE still has the project open
  • confirm Claude Code is running in the same project path
  • run /mcp again
  • if needed, restart Claude Code and reopen the project