PaulSeth/gitee-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITEE_MODE | No | 留空=自动判定；mock=强制演示；real=强制真实（缺 token 自动回退 mock 并告警）。 | |
| GITEE_ACCESS_TOKEN | No | Gitee 私人令牌（设置 → 私人令牌，勾选 projects 权限）。stargazers/subscribers 接口强制鉴权，无 token 会 401。 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_repo_statsB | 获取 Gitee 仓库统计：star/fork/watch 数、开放 issue 数 |
| list_stargazersA | 列出给仓库点 star 的用户（需 PAT，无凭证走 mock） |
| list_issuesC | 列出仓库 Issue，支持按状态/标签过滤 |
| create_issueB | 在仓库新建 Issue（收需求/建任务） |
| update_issueC | 更新 Issue 状态或标签（自动打标签/关单） |
| generate_changelogB | 基于最近 commit 生成中文 CHANGELOG（Gitee 无原生 API，靠 commits 组合） |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| 仓库快照-jokerbhind/social-media-bot-cn-generic | Gitee 仓库 jokerbhind/social-media-bot-cn-generic 的统计与最近 commit（AI 可读） |
TDQS
Scored across 6 tools
Each tool addresses a distinct resource or action: repo stats, stargazers, issue listing, issue creation, issue updating, and changelog generation. No two tools overlap enough to cause misselection; get_repo_stats returns aggregate counts while list_issues returns issue objects.
All names follow a consistent snake_case verb_noun pattern (get_repo_stats, list_stargazers, list_issues, create_issue, update_issue, generate_changelog). There are no mixed conventions or vague verbs.
Six tools is well-scoped for a focused Gitee assistant covering stats, stargazers, issue management, and changelog. Each tool has a clear purpose and none appear redundant or trivial.
The issue surface has list/create/update but lacks get-issue detail, delete, and commenting, and there is no direct commit or PR access despite the generic server name. These are notable gaps, though some can be worked around via list_issues and update_issue.