TIMI CC MCP Patch Worker
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TIMI CC MCP Patch Workergenerate a patch to fix the login bug"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
TIMI CC MCP Patch Worker
一个可本地安装、通过 STDIO 运行的 MCP 服务。它把调用方明确提供的代码上下文发送到 TIMI CC 的 OpenAI-compatible Responses 接口,并返回经过本地路径校验的 Git unified diff;它不会扫描或修改你的仓库。
非 TIMI CC 官方项目。外部模型调用会发送数据并可能产生费用,请先阅读 SECURITY.md。
功能
同步生成或审查候选补丁:
generate_patch、review_patch后台长任务:
submit_patch_job、get_patch_job、get_patch_result、cancel_patch_job本地能力查询:
get_capabilities(不调用 API)Responses SSE 流式接收,避免长请求期间完全无活动
严格限制补丁只能修改
allowed_paths中的路径拒绝二进制补丁、越权路径和超限响应
只持久化任务摘要、哈希、聚合进度和已校验结果,不持久化完整提示词、文件上下文或推理内容
Related MCP server: CodePeel MCP Server
安装
需要 Python 3.10 或更高版本。
git clone https://github.com/prelearn-code/timicc-mcp.git
cd timicc-mcp
python -m venv .venvLinux/macOS:
.venv/bin/python -m pip install -U pip
.venv/bin/python -m pip install -e .
export TIMICC_API_KEY="your-key"Windows PowerShell:
.venv\Scripts\python.exe -m pip install -U pip
.venv\Scripts\python.exe -m pip install -e .
$env:TIMICC_API_KEY = "your-key"不要把真实密钥写进 Git、TOML 示例或命令历史。推荐通过操作系统的密钥管理或在启动 MCP 客户端前设置环境变量。
接入 Codex
将 config.example.toml 复制到 ~/.codex/config.toml,并替换 Python 的绝对路径。Windows 的 command 应改为类似:
command = "C:/absolute/path/timicc-mcp/.venv/Scripts/python.exe"重启 Codex 后运行 codex mcp list,或在 Codex 中输入 /mcp。示例使用 env_vars 转发已存在的环境变量,并将工具审批设为 prompt,因为每次模型调用都可能发送代码并产生费用。
其他支持 STDIO 的 MCP 客户端可用相同入口启动:
/absolute/path/.venv/bin/python -m timicc_worker.server配置
环境变量 | 用途 | 默认值 |
| API 密钥(也兼容 | 无 |
| Responses API 地址 |
|
| 额外允许的模型 ID,逗号分隔 | 无 |
| 后台任务数据库目录 | 操作系统的用户 state 目录 |
| 后台并发数 |
|
默认允许 gpt-5.6-sol、gpt-5.5 和 gpt-5.4。如果兼容网关提供其他 gpt-* 模型,可通过 TIMICC_MODELS 显式添加。
开发与验证
测试不会调用真实 API:
.venv/bin/python -m pip install -e ".[dev]"
.venv/bin/python -m pytest -q
.venv/bin/python -m buildGitHub Actions 会在 Linux、Windows 和 macOS 的 Python 3.10/3.13 上运行相同验证。
安全模型
返回的补丁始终是不可信候选内容。调用方仍需审查完整 diff、应用补丁并运行格式化、lint、构建和测试。allowed_paths 只能约束输出补丁路径,不能识别输入中是否包含敏感数据。
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceEnables multi-agent code review with P0/P1/P2 severity scoring by orchestrating locally installed AI CLIs (Claude, Codex) to perform parallel analysis, deterministic scoring, and consensus-building on git diffs.2

CodePeel MCP Serverofficial
FlicenseAqualityCmaintenanceEnables AI agents to review code diffs for bugs, security issues, and bad patterns, and generate fixes.4- Flicense-qualityCmaintenanceFetches, summarizes, and reviews GitHub code diffs with asynchronous processing for large diffs.
- AlicenseBqualityBmaintenanceGenerates or reviews Git unified diffs via DeepSeek API with local path validation, enabling secure patch suggestions without scanning repositories.7MIT
Related MCP Connectors
Git-native policy layer for AI agents: check_action verdicts against rules approved via PR.
Agentic code review, no signup to try: reality gates + frontier-model review, with veto.
Live PR/MR code reviews via review_url_code. OAuth or portal Bearer auth.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prelearn-code/timicc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server