@codacy/codacy-mcp 0.6.6 → 0.6.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,11 +1,17 @@
1
1
  # Codacy MCP Server
2
2
 
3
+ [![Codacy Badge](https://app.codacy.com/project/badge/Grade/7be4b119dc1e420198f3495017b57c89)](https://app.codacy.com/gh/codacy/codacy-mcp-server/dashboard?utm_source=gh&utm_medium=referral&utm_content=&utm_campaign=Badge_grade)
4
+
3
5
  MCP Server for the Codacy API, enabling access to repositories, files, quality, coverage, security and more.
4
6
 
5
7
  ## Features / Tools
6
8
 
7
9
  The following tools are available through the Codacy MCP Server:
8
10
 
11
+ ### Repository Setup and Management
12
+
13
+ - `codacy_setup_repository`: Add or follow a repository in Codacy if not already present. This tool ensures the repository is registered with Codacy, allowing further analysis and management.
14
+
9
15
  ### Organization and Repository Management
10
16
 
11
17
  - `codacy_list_organizations`: List organizations with pagination support.
@@ -87,6 +93,8 @@ Ensure your machine has the following tools installed:
87
93
  - node.js
88
94
  - ensure that the `npx` command runs without issues.
89
95
 
96
+ For local analysis, the MCP Server requires the [Codacy CLI](https://github.com/codacy/codacy-cli-v2) to be installed. If it is not available, the MCP Server will attempt to install it for you. Codacy CLI v2 runs on macOS, Linux, and Windows (only with WSL).
97
+
90
98
  ### Personal API Access Token
91
99
 
92
100
  Get your Codacy's Account API Token from your [Codacy Account](https://app.codacy.com/account/access-management).
@@ -42,7 +42,7 @@ export const repositorySchema = {
42
42
  ...organizationSchema,
43
43
  repository: {
44
44
  type: 'string',
45
- description: "Repository name on the Git provider. Try to extract it from the repository's git remote URL using 'git remote -v', it should be something like this for gh:'https://github.com/<owner>/<repository>.git' for gl:'https://gitlab.com/<owner>/<repository>.git' for bb:'https://bitbucket.org/<owner>/<repository>.git'.",
45
+ description: "Repository name on the Git provider. Try to extract it from the repository's git remote URL using 'git remote -v', it should be something like this for gh:'https://github.com/<owner>/<repository>.git' for gl:'https://gitlab.com/<owner>/<repository>.git' for bb:'https://bitbucket.org/<owner>/<repository>.git'.",
46
46
  },
47
47
  };
48
48
  export const defaultPagination = {
@@ -41,6 +41,6 @@ export const cliAnalyzeTool = {
41
41
  default: '',
42
42
  },
43
43
  },
44
- required: ['provider', 'organization', 'repository', 'rootPath'],
44
+ required: ['rootPath'],
45
45
  },
46
46
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codacy/codacy-mcp",
3
- "version": "0.6.6",
3
+ "version": "0.6.8",
4
4
  "description": "Codacy MCP server",
5
5
  "license": "MIT",
6
6
  "author": "Codacy",