You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/codacy-guardrails/codacy-guardrails-getting-started.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,23 +83,22 @@ It will create a folder in your local repository called **.codacy** with all nee
83
83
The IDE extension will ignore any CLI version already installed (e.g. through brew or other package manager) on the machine.
84
84
85
85
86
-
### 3. Install MCP Server
86
+
### 3. Check if the Codacy MCP Server is properly setup
87
87
88
-
#### a. Add the Codacy MCP Server
88
+
Codacy MCP Server will be installed automatically when starting the extension, and an instructions file will be created in your workspace.
89
89
90
-
In the Codacy Extension tab, click **Add Codacy MCP Server**
90
+
If you don't want Guardrails to automatically generate the instructions file, go to the extension's settings and set the instructions generation setting to manual.
### 5. After everything is set up, you should now be able to interact with Codacy via AI chat.
101
+
### 4. After everything is set up, you should now be able to interact with Codacy via AI chat.
103
102
* Remember that for you to be able to interact with Codacy MCP server, you must be on the `Agent` mode of the chat, not the default `Ask` mode.
104
103
* If you're still having issues with the MCP server, try to run the command `Preferences: Open User Settings (JSON)`, look for the Codacy MCP server settings and right on top of it you'll should see a `Start` option. Click on it and, if unsuccessful, go to `View > Debug Console` and check for errors. Don't forget to ensure you have `node.js` and `npx` installed and set up.
0 commit comments