Junie MCP Setup: .junie/mcp/mcp.json for CLI and /mcp Command

• Project: .junie/mcp/mcp.json at the project root. You can commit it for the team.
• User: ~/.junie/mcp/mcp.json. Private to you and used in every project.

{
  "mcpServers": {
    "Context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    },
    "RemoteServer": {
      "url": "https://example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Local servers take command, args and an optional env object. Remote servers take url and an optional headers object. Do not commit secrets in the project file.

• /mcp lists servers with their status: Starting, Active, Inactive, Disabled, Failed or Authorization required.
• From the list you can enable, disable, modify or delete a server.
• Press Ctrl+A inside /mcp to open the server registry. Press it again to set up a server from scratch with the MCP Installation Assistant.
• In ACP clients /mcp is read only, so edit the JSON files directly.

• A remote server that needs OAuth shows Authorization required. Select it, choose Authorize, log in in the browser, and check that it turns Active.
• Failed can mean invalid config, failed auth, missing dependencies or a crash.
• Servers added through the Installation Assistant or imported from mcp.json are enabled by default.

• --mcp-location <path> adds a folder to search for MCP servers. You can repeat it.
• --mcp-default-locations (default true) turns loading from the default user and project locations on or off.
• The same options exist as mcp-locations and mcp-default-locations in ~/.junie/config.json.

The Junie plugin settings have an MCP settings page. Its Add button opens an mcp.json file, and server entries go under the mcpServers key.