TIMI CC MCP Patch Worker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMICC_MODELS | No | Comma-separated list of additional allowed model IDs | |
| OPENAI_API_KEY | No | Alternative API key (alias for TIMICC_API_KEY) | |
| TIMICC_API_KEY | No | API key (also compatible with OPENAI_API_KEY) | |
| TIMICC_BASE_URL | No | Responses API URL | https://timicc.com |
| TIMICC_STATE_DIR | No | Directory for background job database | |
| TIMICC_JOB_WORKERS | No | Number of background workers | 2 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_patchC | Generate a validated candidate unified diff without editing the repository. |
| review_patchA | Review an untrusted candidate patch and return a corrected replacement diff, or an empty patch when no correction is justified. |
| submit_patch_jobC | Submit a long-running patch generation job and return immediately. |
| get_patch_jobC | Get the current status of a background patch job. |
| get_patch_resultB | Return a completed validated patch job result, or its current status. |
| cancel_patch_jobB | Request cancellation of a background patch job. |
| get_capabilitiesA | Return local worker capabilities without calling the external model. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools are clearly distinct: generate_patch and review_patch handle direct patch operations, while submit/get/get/cancel_patch_job manage background jobs. Some overlap exists between get_patch_job and get_patch_result, but descriptions clarify that one returns status and the other returns the final result, so confusion is unlikely.
All tool names follow a consistent verb_noun pattern using snake_case. Verbs (generate, review, submit, get, cancel) are descriptive and uniformly formatted, and nouns (patch, patch_job, patch_result, capabilities) are logical and predictable.
With 7 tools, the server is well-scoped for its purpose. It covers both synchronous patch generation/review and asynchronous job management without unnecessary bloat, and each tool fits within a clear workflow.
The tool surface covers the core patch lifecycle: generate, review, submit asynchronous job, retrieve status/result, and cancel. A minor gap is the lack of a list-all-jobs or delete-patch operation, but these are not essential for the primary use case.