cann-gitcode-mcp 0.1.0__tar.gz

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.
@@ -0,0 +1,18 @@
1
+ # Python
2
+ __pycache__/
3
+ *.py[cod]
4
+ *.egg-info/
5
+ dist/
6
+ build/
7
+ *.egg
8
+
9
+ # Virtual environment
10
+ venv/
11
+
12
+ # IDE
13
+ .idea/
14
+ .vscode/
15
+ *.swp
16
+
17
+ # Environment
18
+ .env
@@ -0,0 +1,133 @@
1
+ # AGENTS.md — cann-gitcode-mcp
2
+
3
+ Guidelines for AI agents (and humans) contributing to this repository.
4
+
5
+ ## Project Purpose
6
+
7
+ `cann-gitcode-mcp` wraps the GitCode REST API (v5) as an MCP server so that AI assistants (Claude Code, etc.) can perform GitCode operations on behalf of CANN developers. Current scope: Pull Request management. Planned: CI/pipeline tools, repository tools, Issue tools.
8
+
9
+ ## Repository Structure
10
+
11
+ ```
12
+ cann-gitcode-mcp/
13
+ ├── src/cann_gitcode_mcp/
14
+ │ ├── __init__.py # Package metadata
15
+ │ ├── __main__.py # Entry point: python -m cann_gitcode_mcp
16
+ │ ├── server.py # FastMCP instance; wires all tool modules
17
+ │ ├── client.py # GitCodeClient (async httpx wrapper)
18
+ │ └── tools/
19
+ │ ├── __init__.py
20
+ │ └── pull_request.py # 6 PR tools
21
+ ├── tests/
22
+ │ ├── test_pull_request.py
23
+ │ └── test_server.py
24
+ ├── pyproject.toml
25
+ ├── README.md
26
+ ├── CLAUDE.md
27
+ └── AGENTS.md
28
+ ```
29
+
30
+ ## Setup
31
+
32
+ ```bash
33
+ # Activate the virtual environment (if using the repo's venv)
34
+ source venv/bin/activate
35
+
36
+ # Install the package with development dependencies
37
+ uv pip install -e ".[dev]"
38
+ ```
39
+
40
+ If `uv` is not available, use:
41
+
42
+ ```bash
43
+ pip install -e ".[dev]"
44
+ ```
45
+
46
+ Python >= 3.11 is required.
47
+
48
+ ## Running Tests
49
+
50
+ ```bash
51
+ pytest tests/ -v
52
+ ```
53
+
54
+ All tests are unit tests that mock network calls — no real API token is needed.
55
+
56
+ ## API Client
57
+
58
+ `GitCodeClient` (in `src/cann_gitcode_mcp/client.py`) is the only HTTP layer.
59
+
60
+ - **Auto-reads token**: reads `GITCODE_API_TOKEN` from the environment on construction. Raises `ValueError` if unset.
61
+ - **Base URL**: `https://gitcode.com/api/v5` (override with `GITCODE_API_BASE_URL`).
62
+ - **Methods**: `get`, `post`, `patch`, `put`, `delete` — all async, return parsed JSON or `None` (for 204).
63
+ - **Error handling**: raises `RuntimeError` on non-2xx responses with the status code and body.
64
+
65
+ Example usage in a tool:
66
+
67
+ ```python
68
+ client = GitCodeClient() # reads GITCODE_API_TOKEN from env
69
+ data = await client.get("/repos/owner/repo/pulls/1")
70
+ data = await client.post("/repos/owner/repo/pulls", json={"title": "fix", "head": "dev", "base": "main"})
71
+ ```
72
+
73
+ ## How to Add a New Tool
74
+
75
+ Follow these steps exactly:
76
+
77
+ ### 1. Create the tool file
78
+
79
+ Create `src/cann_gitcode_mcp/tools/<domain>.py`. The file must:
80
+
81
+ - Import `FastMCP` from `mcp.server.fastmcp` and `GitCodeClient` from `cann_gitcode_mcp.client`.
82
+ - Define a module-level `_client: GitCodeClient | None = None` and a `_get_client()` helper.
83
+ - Define a single public function `register_<domain>_tools(mcp: FastMCP) -> None`.
84
+ - Inside that function, define each tool as an `async def` decorated with `@mcp.tool()`.
85
+
86
+ Rules for tool functions:
87
+ - Must be `async def`.
88
+ - Must return `str` (JSON, produced with `json.dumps(..., ensure_ascii=False)`).
89
+ - Must have a docstring — the first line is the MCP tool description; use `Args:` sections for parameters.
90
+ - Must include type annotations on all parameters.
91
+
92
+ ### 2. Register in server.py
93
+
94
+ Add two lines to `src/cann_gitcode_mcp/server.py`:
95
+
96
+ ```python
97
+ from cann_gitcode_mcp.tools.<domain> import register_<domain>_tools
98
+ register_<domain>_tools(mcp)
99
+ ```
100
+
101
+ ### 3. Add tests
102
+
103
+ Create `tests/test_<domain>.py`. Use `unittest.mock.AsyncMock` / `patch` to mock `GitCodeClient` methods. Never make real HTTP requests in tests.
104
+
105
+ Pattern for accessing a registered tool function:
106
+
107
+ ```python
108
+ tool_fn = mcp_server._tool_manager._tools["<tool_name>"].fn
109
+ result = await tool_fn(owner="org", repo="repo", ...)
110
+ ```
111
+
112
+ ### 4. Run tests
113
+
114
+ ```bash
115
+ pytest tests/ -v
116
+ ```
117
+
118
+ All existing and new tests must pass before committing.
119
+
120
+ ## Important Constraints
121
+
122
+ - **All tool functions must be `async def`** — synchronous tools will fail at runtime.
123
+ - **Return type is always `str`** — serialize with `json.dumps(result, indent=2, ensure_ascii=False)`.
124
+ - **Registration pattern** — tools must be registered via `@mcp.tool()` inside a `register_*_tools(mcp)` function; do not call `mcp.tool()` at module import time.
125
+ - **No global state beyond `_client`** — the module-level `_client` singleton is reset between test fixtures via `patch`.
126
+ - **Token is required** — `GitCodeClient()` raises `ValueError` if `GITCODE_API_TOKEN` is not set; tests must patch the env or the client.
127
+
128
+ ## GitCode API Reference
129
+
130
+ - Base URL: `https://gitcode.com/api/v5`
131
+ - Authentication: `Authorization: Bearer <token>` header
132
+ - PR endpoints: `/repos/{owner}/{repo}/pulls[/{number}[/merge|comments|files]]`
133
+ - Full API docs: consult GitCode platform documentation
@@ -0,0 +1,132 @@
1
+ # CLAUDE.md — cann-gitcode-mcp
2
+
3
+ ## Project Overview
4
+
5
+ `cann-gitcode-mcp` is an MCP (Model Context Protocol) server that exposes GitCode API operations as MCP tools for CANN developers. It wraps GitCode's REST API (v5, base URL `https://gitcode.com/api/v5`) so that Claude Code and other MCP clients can perform GitCode actions (create PRs, list PRs, merge, comment, etc.) directly from a conversation. The package name is `cann-gitcode-mcp`; the importable Python module is `cann_gitcode_mcp`.
6
+
7
+ ## Architecture
8
+
9
+ ```
10
+ src/cann_gitcode_mcp/
11
+ ├── __init__.py # Package version / public exports
12
+ ├── __main__.py # python -m cann_gitcode_mcp entry point → calls server.main()
13
+ ├── server.py # FastMCP instance + wires in all tool modules
14
+ ├── client.py # GitCodeClient: async HTTP client wrapping httpx
15
+ └── tools/
16
+ ├── __init__.py
17
+ └── pull_request.py # register_pull_request_tools(mcp) — 6 PR tools
18
+ ```
19
+
20
+ - **`server.py`** — creates the `FastMCP("gitcode")` instance and calls every `register_*_tools(mcp)` function. This is the single wiring point.
21
+ - **`client.py`** — `GitCodeClient` reads `GITCODE_API_TOKEN` from the environment, sets up an `httpx.AsyncClient`, and provides `get / post / patch / put / delete` async helpers.
22
+ - **`tools/`** — each file owns one domain (pull requests, issues, repos, …). Tools are registered via `@mcp.tool()` inside a `register_*_tools(mcp: FastMCP)` function.
23
+
24
+ ## Adding New Tools
25
+
26
+ 1. Create `src/cann_gitcode_mcp/tools/<domain>.py`.
27
+ 2. Define `register_<domain>_tools(mcp: FastMCP) -> None` that decorates each async function with `@mcp.tool()`.
28
+ 3. Import and call the registration function in `server.py`.
29
+ 4. Add tests in `tests/test_<domain>.py` (see Testing Patterns below).
30
+
31
+ Example skeleton:
32
+
33
+ ```python
34
+ # src/cann_gitcode_mcp/tools/issue.py
35
+ from __future__ import annotations
36
+ import json
37
+ from mcp.server.fastmcp import FastMCP
38
+ from cann_gitcode_mcp.client import GitCodeClient
39
+
40
+ _client: GitCodeClient | None = None
41
+
42
+ def _get_client() -> GitCodeClient:
43
+ global _client
44
+ if _client is None:
45
+ _client = GitCodeClient()
46
+ return _client
47
+
48
+ def register_issue_tools(mcp: FastMCP) -> None:
49
+
50
+ @mcp.tool()
51
+ async def get_issue(owner: str, repo: str, number: int) -> str:
52
+ """Get details of a GitCode issue.
53
+
54
+ Args:
55
+ owner: Repository namespace
56
+ repo: Repository name
57
+ number: Issue number
58
+ """
59
+ client = _get_client()
60
+ result = await client.get(f"/repos/{owner}/{repo}/issues/{number}")
61
+ return json.dumps(result, indent=2, ensure_ascii=False)
62
+ ```
63
+
64
+ Then in `server.py`:
65
+
66
+ ```python
67
+ from cann_gitcode_mcp.tools.issue import register_issue_tools
68
+ register_issue_tools(mcp)
69
+ ```
70
+
71
+ ## Development Commands
72
+
73
+ ```bash
74
+ # Install with dev dependencies
75
+ uv pip install -e ".[dev]"
76
+
77
+ # Run the test suite
78
+ pytest
79
+
80
+ # Run with verbose output
81
+ pytest -v
82
+
83
+ # Start the MCP server (stdio transport)
84
+ python -m cann_gitcode_mcp
85
+ ```
86
+
87
+ ## Code Style
88
+
89
+ - **Python 3.11+** — use `X | Y` union types, `from __future__ import annotations` at the top of every file.
90
+ - **Async** — all tool functions must be `async def`.
91
+ - **Type hints** — all function parameters and return types must be annotated.
92
+ - **Docstrings** — every tool function must have a docstring; the first line becomes the MCP tool description. Use `Args:` sections for parameter documentation.
93
+ - **Return type** — all tools return `str` (JSON-serialised with `json.dumps(..., ensure_ascii=False)`).
94
+ - **No bare exceptions** — let errors propagate from `GitCodeClient`; the MCP framework will surface them to the client.
95
+
96
+ ## Testing Patterns
97
+
98
+ Tests live in `tests/`. The project uses `pytest-asyncio` with `asyncio_mode = "auto"`.
99
+
100
+ Key pattern — mock `GitCodeClient` methods so tests never hit the network:
101
+
102
+ ```python
103
+ import pytest
104
+ from unittest.mock import AsyncMock, patch
105
+ from mcp.server.fastmcp import FastMCP
106
+ from cann_gitcode_mcp.tools.pull_request import register_pull_request_tools
107
+
108
+ @pytest.fixture
109
+ def mcp_server():
110
+ server = FastMCP("test")
111
+ with patch("cann_gitcode_mcp.tools.pull_request._client", None), \
112
+ patch.dict("os.environ", {"GITCODE_API_TOKEN": "test-token"}):
113
+ register_pull_request_tools(server)
114
+ yield server
115
+
116
+ async def test_get_pull_request(mcp_server):
117
+ tool_fn = mcp_server._tool_manager._tools["get_pull_request"].fn
118
+ fake_pr = {"number": 1, "title": "fix: something"}
119
+ with patch("cann_gitcode_mcp.tools.pull_request.GitCodeClient.get",
120
+ new_callable=AsyncMock, return_value=fake_pr):
121
+ result = await tool_fn(owner="org", repo="repo", number=1)
122
+ assert '"number": 1' in result
123
+ ```
124
+
125
+ Use `mcp_server._tool_manager._tools["<tool_name>"].fn` to get the raw async callable for a registered tool.
126
+
127
+ ## Environment
128
+
129
+ | Variable | Required | Description |
130
+ |----------|----------|-------------|
131
+ | `GITCODE_API_TOKEN` | Yes | Personal access token from GitCode settings |
132
+ | `GITCODE_API_BASE_URL` | No | Override API base (default: `https://gitcode.com/api/v5`) |
@@ -0,0 +1,190 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to the Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by the Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding any notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ Copyright 2026 shengnan
179
+
180
+ Licensed under the Apache License, Version 2.0 (the "License");
181
+ you may not use this file except in compliance with the License.
182
+ You may obtain a copy of the License at
183
+
184
+ http://www.apache.org/licenses/LICENSE-2.0
185
+
186
+ Unless required by applicable law or agreed to in writing, software
187
+ distributed under the License is distributed on an "AS IS" BASIS,
188
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
189
+ See the License for the specific language governing permissions and
190
+ limitations under the License.
@@ -0,0 +1,149 @@
1
+ Metadata-Version: 2.4
2
+ Name: cann-gitcode-mcp
3
+ Version: 0.1.0
4
+ Summary: CANN GitCode MCP Server - GitCode platform tools for CANN developers
5
+ Project-URL: Homepage, https://gitcode.com/shengnan666/cann-gitcode-mcp
6
+ Project-URL: Repository, https://gitcode.com/shengnan666/cann-gitcode-mcp
7
+ Project-URL: Issues, https://gitcode.com/shengnan666/cann-gitcode-mcp/issues
8
+ Author-email: shengnan <shengnan1126@yeah.net>
9
+ License-Expression: Apache-2.0
10
+ License-File: LICENSE
11
+ Keywords: cann,gitcode,mcp,model-context-protocol
12
+ Classifier: Development Status :: 3 - Alpha
13
+ Classifier: Intended Audience :: Developers
14
+ Classifier: License :: OSI Approved :: Apache Software License
15
+ Classifier: Programming Language :: Python :: 3
16
+ Classifier: Programming Language :: Python :: 3.11
17
+ Classifier: Programming Language :: Python :: 3.12
18
+ Classifier: Programming Language :: Python :: 3.13
19
+ Classifier: Topic :: Software Development :: Libraries
20
+ Requires-Python: >=3.11
21
+ Requires-Dist: httpx>=0.27
22
+ Requires-Dist: mcp>=1.0
23
+ Provides-Extra: dev
24
+ Requires-Dist: build>=1.0; extra == 'dev'
25
+ Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
26
+ Requires-Dist: pytest>=8.0; extra == 'dev'
27
+ Requires-Dist: twine>=6.0; extra == 'dev'
28
+ Description-Content-Type: text/markdown
29
+
30
+ # cann-gitcode-mcp
31
+
32
+ [![PyPI version](https://img.shields.io/pypi/v/cann-gitcode-mcp)](https://pypi.org/project/cann-gitcode-mcp/)
33
+ [![Python](https://img.shields.io/pypi/pyversions/cann-gitcode-mcp)](https://pypi.org/project/cann-gitcode-mcp/)
34
+ [![License](https://img.shields.io/pypi/l/cann-gitcode-mcp)](https://github.com/shengnan666/cann-gitcode-mcp/blob/main/LICENSE)
35
+
36
+ CANN GitCode MCP 服务器 —— 为 CANN 开发者提供的 GitCode 平台 MCP 工具集。
37
+
38
+ ## 简介
39
+
40
+ `cann-gitcode-mcp` 是一个基于 [MCP(Model Context Protocol)](https://modelcontextprotocol.io/) 的服务器,将 GitCode API 操作封装为 MCP 工具,供 Claude Code 及其他 MCP 客户端直接调用。
41
+
42
+ CANN 社区的代码托管在 GitCode 平台,本项目为 CANN 开发者提供在 AI 助手中操作 GitCode 仓库(Pull Request、流水线、Issue 等)的能力,无需离开对话界面即可完成常见研发工作流。
43
+
44
+ ## 安装
45
+
46
+ ```bash
47
+ pip install cann-gitcode-mcp
48
+ ```
49
+
50
+ ## 配置
51
+
52
+ ### 1. 获取 GitCode API Token
53
+
54
+ 在 [GitCode 用户设置](https://gitcode.com/profile/tokens) 中生成个人访问令牌。
55
+
56
+ ### 2. 设置环境变量
57
+
58
+ ```bash
59
+ export GITCODE_API_TOKEN=your_token_here
60
+ ```
61
+
62
+ ### 3. 与 Claude Code 集成
63
+
64
+ 在 Claude Code 的 MCP 配置文件中添加:
65
+
66
+ ```json
67
+ {
68
+ "mcpServers": {
69
+ "gitcode": {
70
+ "command": "cann-gitcode-mcp",
71
+ "env": {
72
+ "GITCODE_API_TOKEN": "your_token_here"
73
+ }
74
+ }
75
+ }
76
+ }
77
+ ```
78
+
79
+ 或使用模块方式:
80
+
81
+ ```json
82
+ {
83
+ "mcpServers": {
84
+ "gitcode": {
85
+ "command": "python",
86
+ "args": ["-m", "cann_gitcode_mcp"],
87
+ "env": {
88
+ "GITCODE_API_TOKEN": "your_token_here"
89
+ }
90
+ }
91
+ }
92
+ }
93
+ ```
94
+
95
+ 配置完成后重启 Claude Code,即可在对话中使用所有 GitCode 工具。
96
+
97
+ ## 可用工具
98
+
99
+ ### Pull Request
100
+
101
+ | 工具名 | 说明 |
102
+ |--------|------|
103
+ | `create_pull_request` | 创建 Pull Request |
104
+ | `list_pull_requests` | 列出仓库的 Pull Request(支持状态、排序等过滤) |
105
+ | `get_pull_request` | 获取指定 PR 的详细信息 |
106
+ | `merge_pull_request` | 合并 Pull Request |
107
+ | `comment_pull_request` | 在 PR 上发表评论 |
108
+ | `get_pull_request_files` | 获取 PR 的变更文件列表 |
109
+
110
+ ## 环境变量
111
+
112
+ | 变量 | 必填 | 说明 |
113
+ |------|------|------|
114
+ | `GITCODE_API_TOKEN` | 是 | GitCode 个人访问令牌 |
115
+ | `GITCODE_API_BASE_URL` | 否 | API 地址覆盖(默认 `https://gitcode.com/api/v5`) |
116
+
117
+ ## 路线图
118
+
119
+ - **Issue 工具**:Issue 增删改查、评论管理
120
+ - **仓库工具**:分支管理、文件读取、提交历史
121
+ - **流水线/CI 工具**:触发 CANN CI 流水线、查询流水线状态
122
+
123
+ ## 开发
124
+
125
+ ```bash
126
+ # 安装开发依赖
127
+ pip install -e ".[dev]"
128
+
129
+ # 运行测试
130
+ pytest
131
+
132
+ # 构建包
133
+ python -m build
134
+
135
+ # 上传到 PyPI
136
+ twine upload dist/*
137
+ ```
138
+
139
+ ## 版本规则
140
+
141
+ 本项目遵循 [语义化版本](https://semver.org/lang/zh-CN/):
142
+
143
+ - `0.x.y` — 早期开发阶段,接口可能不兼容变更
144
+ - `1.0.0` — 工具集稳定后的首个正式版本
145
+ - MAJOR.MINOR.PATCH — 不兼容变更.新功能.修复
146
+
147
+ ## 许可证
148
+
149
+ [Apache License 2.0](LICENSE)