Githits

MCP开发工具

提供方 githits-com

开发工具 未标注 会话登录 社区 / 第三方 CursorCodexZed

GitHits MCP is an OSS context layer for the full software development lifecycle, giving AI agents access to code search, package docs, real-world examples, dependency metadata, vulnerabilities, changelogs, and upgrade evidence.

一句话选型结论

按资料字段整理

Githits 属于开发工具类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Cursor、Codex、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

mcpdeveloper toolscode search

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Githits当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方githits-com上游标注的维护方 githits-com
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

17.1 KB
来自项目仓库与上游目录的原文,未做删改

GitHits CLI

The infrastructure layer connecting agents to the open-source ecosystem.

Website ·
Documentation ·

GitHits connects AI coding agents to public open-source evidence across the
full software development lifecycle: discovery, planning, research,
implementation, debugging, and maintenance.

The CLI runs a local MCP server that your
coding tool starts on demand. Agents can then search indexed package and
repository source, read exact files and documentation pages, inspect package
health, compare dependency upgrades, and find source-cited examples from real
open-source projects when model knowledge and local repository context are not
enough.

Want to use GitHits as part of your agent harness or software factory? Check out
our public API documentation.

Quick Start```sh

npx githits@latest init


`init` signs you in, detects supported coding tools, and configures GitHits for
the tools you select. It uses the local stdio MCP except for Cursor, whose
direct setup uses the hosted remote MCP.

Automatic setup currently supports Claude Code, Cursor, Windsurf,
VS Code / Copilot, Cline, Claude Desktop, Codex CLI, Pi, Gemini CLI,
Google Antigravity, OpenCode, Hermes Agent, Zed, Junie, Qwen Code,
Kiro, Kilo Code, Factory Droid, and Amazon Q CLI.

After setup, open your coding agent and work normally. Many agents call GitHits
when they need source-backed context. If your agent starts guessing, prompt it
directly:```text
Use GitHits Code Navigation to inspect npm:express. Find how middleware
errors are handled, read the relevant source, and explain the fix before
editing code.

What GitHits Adds

GitHits is designed for the point where an agent needs evidence from the
broader open-source ecosystem, not just model memory or local repo context:

Capability MCP tools CLI commands
Tool orientation quick_start —
Code examples get_example githits example
Inventory browsing list githits list
Code and documentation search search, search_status, grep githits search, githits search-status, githits grep
Read source files or documentation sections read githits read [path]
Package inspection pkg_info, pkg_vulns, pkg_deps, pkg_changelog, pkg_upgrade_review githits pkg ...

Use GitHits when your agent needs to:

  • discover, plan, or research how OSS projects solve a vague issue or unfamiliar error
  • find broad prior art or rare needle-in-the-haystack examples across repositories
  • inspect source, tests, symbols, or docs for a known package or repository
  • verify how a dependency actually behaves before changing code
  • debug stack traces that point into third-party code
  • review package health, licenses, vulnerabilities, dependencies, and changelogs
  • compare dependency upgrades using factual evidence

Examples

Find prior art across open source:```sh
npx githits@latest example "HTTP retries with exponential backoff in Python"


Search indexed code, docs, and symbols for a dependency:```sh
npx githits@latest search "router middleware" --in npm:express
npx githits@latest search '"body parser" OR multer' --in npm:express --source docs
npx githits@latest search "debounce" --in npm:lodash --source symbol

Read and grep dependency source without cloning:```sh
npx githits@latest code files npm:express lib
npx githits@latest code read npm:express lib/router/index.js --lines 120-200
npx githits@latest grep 'router.use' npm:express --path-prefix lib/


Inspect package health and upgrade evidence:```sh
npx githits@latest pkg info npm:express
npx githits@latest pkg vulns npm:lodash@4.17.20 --severity high
npx githits@latest pkg deps npm:express@4.18.2 --depth 2
npx githits@latest pkg changelog npm:express --from 4.18.2 --to 5.2.1
npx githits@latest pkg upgrade-review npm:zod@4.3.6 --to 4.4.3

Browse and read package documentation:```sh
npx githits@latest docs list npm:express
npx githits@latest docs read <docs-read-target> --lines 20-80


## Source Diffs

`githits code diff` and the public MCP `code_diff` tool are available by default.
Compare exact package versions or public repository refs, for example:```sh
githits code diff npm:express 5.2.0..5.2.1 --stat
githits code diff npm:express 5.2.0..5.2.1 --patch -- &#x27;lib/**/*.js&#x27;

Package diffs are repository-wide unless narrowed by an explicit path glob.
Raw diffs do not prove upgrade safety. See source diff
for bounds, patch safety, and supported addressing. Hosted MCP availability
requires adoption of the released @githits/mcp package and deployment.

Target Resolution

resolve_target / githits resolve turns a fuzzy, misspelled or ambiguous public
package, repository or documentation-site name into ranked canonical targets.
It is available by default in the CLI, local MCP and public MCP package.
Canonical targets skip resolution; uncertain identity needs an explicit choice.
See target resolution for continuation
rules and limits. Hosted MCP and plugins receive it after the released package
is adopted and deployed.

Research

research / githits research answers a question about one public package or
repository with a verified answer that cites its sources. It is available by
default in the CLI, local MCP and public MCP package:```sh
githits research "How does FastAPI dependency injection resolve nested dependencies?"
githits research npm:express "Where is router dispatch implemented?"
githits research --thread <thread-id> "How does that interact with route parameters?"


Omit the target to let GitHits identify it from the question; reuse a returned
thread ID for follow-ups. Answers usually take 30 seconds to a few minutes.
Questions are sent to GitHits, so never include credentials, personal data or
private code. Research may return a rate-limit or daily-limit error; the message says when to
retry, and the daily limit resets at 00:00 UTC. See
research for sources, threads and limits.
Hosted MCP and plugins receive it after the released package is adopted and
deployed.

## Supported Sources

GitHits works with package and repository targets such as:

- package specs: `npm:react`, `npm:react@18.2.0`, `pypi:requests`, `crates:serde`
- GitHub repos: `https://github.com/expressjs/express`, `github:expressjs/express@main`

Package inspection supports npm, PyPI, Hex, Crates, NuGet, Maven, Packagist,
RubyGems, Go, Swift, vcpkg, and Zig. Advisory data is unavailable for vcpkg and
Zig; dependency graph support varies by registry. `cargo:` is an input alias for
`crates:` (public crates.io); canonical registry identities remain `crates`.

## License Filtering

Code example search supports license filtering:

- `strict` is the default and filters repositories with copyleft or undeclared licenses
- `custom` uses your account blocklist configured at githits.com
- `yolo` disables license filtering```sh
npx githits@latest example &quot;async file reading&quot; --lang python --license strict

Authentication

Normal local setup is handled by:```sh
npx githits@latest init


For manual login:```sh
npx githits@latest login

Browser OAuth is recommended for local development. Credentials are stored in
the system keychain by default and refreshed automatically. Useful flags:

  • init --no-browser or login --no-browser prints the login URL instead of launching a browser
  • init --port or login --port fixes the loopback callback port
  • login --force re-authenticates even if you are already logged in

The OAuth callback always listens on the machine where GitHits is running.
When GitHits runs over SSH and the browser runs locally, forward the selected
port from the browser machine:```sh
ssh -N -L 8765:127.0.0.1:8765 user@remote-host


With that tunnel open, run GitHits on the remote machine using the same port:```sh
npx githits@latest init --no-browser --port 8765

Open the URL printed by GitHits in the local browser. Replace
user@remote-host with the SSH destination you normally use. The same flags
work with githits login after setup.

Browser OAuth is interactive. For CI and other unattended environments, supply
GITHITS_API_TOKEN through the environment's secret manager.

Keychain Prompts and File Storage

GitHits uses the system keychain by default because OAuth credentials include a
refresh token. On macOS this means Keychain Access; on Windows it means
Credential Manager; on Linux it means the available Secret Service or keyring
backend.

If macOS shows a prompt such as "githits wants to access ... in your keychain",
choose Always Allow when you trust the installed githits CLI. GitHits
cannot customize that operating-system prompt; it is generated by macOS.

GitHits also writes a small non-secret metadata file so recent startup checks do
not need to read the keychain. The keychain is only read when GitHits needs the
token, for example during a tool call, token refresh, githits auth status, or a
login check after metadata is stale or expired.

If your agent keeps showing keychain prompts even after Always Allow, switch
OAuth storage to file mode:```toml

macOS/Linux: ~/.config/githits/config.toml, or $XDG_CONFIG_HOME/githits/config.toml

Windows: %APPDATA%\githits\config.toml

[auth]
storage = "file"


The config directory may be empty until you create `config.toml` or GitHits
writes auth metadata. Older macOS installs may have used
`~/Library/Application Support/githits`; GitHits still reads that location for
migration, but new auth config and file storage use `~/.config/githits`.

You can also opt in for one process:```sh
GITHITS_AUTH_STORAGE=file githits login --force

File mode stores OAuth credentials as JSON files under the GitHits config
directory. The files are written with private permissions where the platform
supports it, but they are not encrypted. Any process that can read files as your
operating-system user may be able to read the tokens.

Use file mode only on machines where you trust local user-account access. For CI
and automation, prefer GITHITS_API_TOKEN instead of browser OAuth.

Inspect auth and runtime state with:```sh
npx githits@latest auth status
npx githits@latest doctor


See the authentication docs for
keychain behavior, file storage mode, CI setup, and troubleshooting.

## Manual MCP Setup

If your coding tool is not auto-configured by `init`, add GitHits to its MCP
configuration manually:```json
{
  &quot;mcpServers&quot;: {
    &quot;githits&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [&quot;-y&quot;, &quot;githits@latest&quot;, &quot;mcp&quot;, &quot;start&quot;]
    }
  }
}

Your tool runs this command over stdio. No background daemon or global install
is required.

To remove configuration written by init:```sh
npx githits@latest uninstall


This removes GitHits MCP configuration and guidance written by `init`, while
preserving stored credentials. Run `npx githits@latest logout` separately to
remove credentials. The compatibility form `npx githits@latest init uninstall`
accepts the same `--yes`, `--project`, and `--keep-guidance` options.

## Project Setup

For project-local MCP config, run:```sh
npx githits@latest init --project

Project setup is available only for tools with verified project-local MCP
support. Project config contains no secrets, but it may be committed like other
tooling configuration, so review generated files before adding them to source
control.

Agent-safe non-interactive setup uses staged discovery and explicit install:```sh
npx githits@latest init --detect-agents --json
npx githits@latest init --install-agents cursor,codex-cli


## Plugin and Extension Packaging

The repository and published package provide the plugin and extension assets
used by compatible hosts. Git-based installs also retain the context-file
symlinks (`CLAUDE.md` and `GEMINI.md`) to the canonical `AGENTS.md`:

- `.plugin/plugin.json`
- `.claude-plugin/plugin.json`
- `.claude-plugin/marketplace.json`
- `.codex-plugin/plugin.json`
- `.cursor-plugin/plugin.json`
- `.mcp.json`
- `gemini-extension.json`
- `plugin.json` (Google Antigravity)
- `mcp_config.json` (Google Antigravity)
- `AGENTS.md`
- `CLAUDE.md`
- `GEMINI.md`
- `skills/`

The root skill tree is shared by all supported hosts. Every plugin and extension
install uses the hosted remote MCP, including Claude, Codex, Cursor, Gemini CLI,
Google Antigravity, and VS Code/GitHub Copilot OpenPlugin. Direct `githits init`
setup is a separate path: it installs local stdio configurations for supported
tools except Cursor, which remains remote-only. The repository root is a native
Antigravity plugin through `plugin.json`, `mcp_config.json`, and the shared
`skills/` tree. Generated manifests are refreshed with `bun run plugins:generate`
and validated with `bun run plugins:check`.

Guided `init` installs the four canonical skills (`githits-code`, `githits-mcp`,
`githits-onboarding`, and `githits-package`) only for selected agents. Shared
skill-capable agents use `~/.agents/skills/` at user scope or `.agents/skills/`
at project scope; native-only agents use their verified native skill directory.
Compatible agents reading a shared root can discover those skills. A later
guided run repairs missing skills, and migration removes only the historical
Cline or Junie `githits-mcp/SKILL.md` after the complete shared set is verified.

For Claude Code marketplace installs:```sh
claude plugin marketplace add githits-com/githits-cli
claude plugin install githits@githits-plugins

For Gemini CLI extension installs:```sh
gemini extensions install https://github.com/githits-com/githits-cli


## Command Reference```text
githits init             Connect GitHits to your coding agents
githits uninstall        Remove GitHits MCP configuration and guidance
githits init uninstall   Compatibility alias for `githits uninstall`
githits login            Sign in to your GitHits account
githits logout           Remove stored credentials
githits mcp              Show setup instructions or start the local MCP server
githits mcp start        Always start the local MCP server over stdio
githits example          Find real-world implementations from open source
githits doctor           Diagnose configuration and auth state
githits resolve          Resolve a fuzzy name to canonical targets
githits settings         View and update preferences, privacy, and terms
githits search           Explore repository code, dependencies, docs, and symbols
githits search-status    Check the status of a previous indexed search
githits code             List, read, grep, or diff source
githits pkg              Inspect package metadata, vulnerabilities, deps, and changelogs
githits docs             Browse and read package documentation
githits auth             Manage authentication
githits auth status      Show authentication status

Full CLI reference: https://docs.githits.com/cli/commands

Environment Variables

Most users do not need environment variables. These are the common overrides for
CI, auth storage, and local diagnostics:

Variable Purpose Default
GITHITS_API_TOKEN API token for authentication unset
GITHITS_AUTH_STORAGE Override OAuth storage mode: keychain or file keychain
GITHITS_DISABLE_UPDATE_CHECK Disable npm latest-version update notices unset
GITHITS_TELEMETRY Emit local timing diagnostics to stderr unset

Full reference: https://docs.githits.com/cli/environment-variables

Source Layout

This repository contains the GitHits CLI and reusable MCP package:

  • src/ - CLI commands, local auth, setup flows, and local MCP stdio startup
  • packages/mcp/ - public @githits/mcp package for transport-neutral MCP
    server APIs, tool registration, instructions, and smoke-test helpers
  • packages/core-internal/ - shared workspace implementation used by the CLI
    and MCP package
  • docs/ - implementation notes and contributor guidelines
  • scripts/ - package validation, smoke tests, and development utilities

See CHANGELOG.md for released changes, pending work, and the
current package-version impact.

Development

Requirements:

  • Node.js ^20.18.1 · &gt;=22.13.0
  • Bun
  • Python 3.11 or later for the dependency-upgrade scorer tests (python on
    Windows, python3 elsewhere)

Common commands:```sh
bun install
bun run dev --help
bun test
bun run typecheck
bun run build


When changing MCP tools, CLI commands, shared formatters, auth/error envelopes,
or MCP/CLI parity behavior, also run the relevant smoke suites:```sh
bun run smoke:mcp
bun run smoke:cli

CI also checks the built product without credentials or live backend calls. Run
the same checks locally after bun run build:```sh
bun run smoke:cli:built
bun run smoke:mcp:built


The harness remains on Bun, while product subprocesses execute `dist/cli.js`
with `node` from `PATH`. CI provisions that runtime from `.node-version`.

Secret scanning uses the gitleaks OSS CLI at version 8.30.1. The pre-commit
hook runs `bun run check:gitleaks` on staged changes. Scan the full history
locally with:```sh
gitleaks git --redact --no-banner --no-color .

Install the 8.30.1 binary from the gitleaks releases and put it on PATH.
See secret scanning for the CI
schedule, suppression order, and npm package boundary.

When changing MCP instructions, tool descriptions, or agent-facing behavior,
use the targeted agent evals described in eval/agentic/README.md:sh bun run agent:e2e

License

Apache-2.0

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Githits 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Githits 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Githits 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Githits 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Githits 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Githits 能提供哪些能力?

资料显示能力标签包括 mcp、developer tools、code search、open source。具体工具清单以官方文档为准。

Githits 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。