Colink MCP
Related Servers
Alternatives to Colink MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to read and search code across many git repositories — files at any branch, tag or commit, history, diffs, blame and cross-repo search — over local paths or remote hosts like GitHub, GitLab and Bitbucket. It is read-only by construction, hiding secrets found in files and working with any MCP client over stdio or Streamable HTTP.1460 PyPIApache 2.0
- FlicenseBqualityDmaintenanceProvides LLMs with safe, read-only access to local codebases for searching, reading files, and finding function definitions. All source code remains local, ensuring privacy while enabling AI assistants to explore project structures and functionality.4-
- AlicenseAqualityAmaintenanceTurn any folder or Git repo into safe, token-efficient context for LLMs, AI chats, and coding agents like Claude Code, Codex, and Cursor — local-first GUI, TUI, CLI, and a read-only MCP server with Live Context, agent journal, Smart Ignore, secret/PII redaction, Git scopes, and code compression. Windows, macOS, Linux.839Apache 2.0
- AlicenseAqualityCmaintenanceA read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.5ISC
- AlicenseNot gradedqualityAmaintenanceEnables local LLM tools and agentic IDEs to inspect repository token maps, retrieve clean token-bounded codebase snapshots, and audit code for hardcoded secrets via MCP over stdio.10 npm4MIT
- AlicenseNot gradedqualityAmaintenanceGives ChatGPT and Claude Code policy-scoped access to a local repository checkout, allowing them to list, search, read, edit, and create files, run operator-approved fixture tests, and inspect git diffs. It confines operations to configured paths and resources, and supports an independent read-only review workflow.2 npm5MIT
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.