Colink MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODE_CONTEXT_READ_TOKEN | No | Token used by clients reading the mirror. Must be at least 32 non-whitespace ASCII characters. HTTP MCP clients must send Authorization: Bearer <read token>. | |
| CODE_CONTEXT_SYNC_TOKEN | No | Token used by the local upload process, with upload and read permissions. Must be at least 32 non-whitespace ASCII characters. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | Find available code projects. Context handles are internal, not user-facing labels. |
| repo_overviewA | List code files. Omit snapshot for current code, use 'previous', or reuse an opaque handle. Pass the returned handle to follow-up reads; do not include it in the answer. Only current and previous code are retained. Expired handles require a fresh analysis. |
| read_fileA | Read source to answer code questions; default 200, max 1000 lines. Omit snapshot for current code, use 'previous', or reuse repo_overview's opaque handle for consistent reads. Report code findings, not handles, hashes or synchronization metadata, unless requested. |
| search_codeA | Locate literal, case-sensitive code text with paths and lines. Omit snapshot for current code, use 'previous', or reuse an opaque handle. Keep handles out of the answer. |
| get_diffA | Review the latest code changes against the preceding state; no numbered versions needed. Omit snapshot for current code or reuse its opaque handle. With only one initial state, compare against an empty project. Optional path limits the comparison to one file. |
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 5 tools
Each tool targets a distinct action: listing projects, listing files, reading content, searching, and diffing. The four read tools share a 'snapshot'/opaque-handle mechanism but their core purposes (files vs. content vs. search vs. diff) remain clearly separable.
Four tools follow a verb_noun pattern (list_projects, read_file, search_code, get_diff). repo_overview breaks the pattern as a noun-first name, a minor deviation but still readable.
Five tools is a lean but well-scoped set for a read-only code exploration server. Each tool covers a distinct need without redundancy, though slightly thin overall.
Covers the core read-only lifecycle: discover projects, enumerate files, read content, search text, and view diffs. Minor gaps exist (e.g., no directory-level navigation or metadata/project-detail view), but agents can work around them.