Starcat MCP server
Commit Nov 4, 2026Lets an AI client search, organize, and manage a local knowledge base built from GitHub Stars.
Also known as starcat-app/starcat-cli
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 4, 2026
- License
- MIT
What is Starcat MCP?
Starcat lets an AI client search, organize, and manage a local knowledge base built from GitHub Stars.
Summary generated from the project's README
About Starcat MCP server
Starcat CLI serves as a bridge between AI agents and a local knowledge base built from GitHub Stars. It functions as a stdio MCP server, allowing tools like Claude Code or Codex to interact with your curated repository data. The system is designed to work with the native macOS Starcat app, which manages the core database, permissions, and business logic.
Users can install the CLI on macOS, Linux, or Windows using Homebrew, shell scripts, or PowerShell. To connect an AI client, you must first pair the CLI with the Starcat app using a specific pairing command and then configure your agent with the starcat mcp command. This setup ensures that all read and write operations are subject to the authorization boundaries and audit logging enforced by the main application.
Developers can use specific commands to manage their collections, such as searching for repositories, viewing READMEs, or checking statistics. The CLI includes safety features like dry-run defaults for write operations, requiring an explicit apply flag to persist changes to your knowledge base.
What you can do with it
- 1Search local repository knowledgeAn AI agent can search through your starred GitHub repositories to find specific technical information.
- 2Retrieve repository contextYou can ask an AI to summarize or read the documentation of a specific repository in your collection.
- 3Organize repositories with tagsAn AI client can add descriptive tags to a repository to improve future organization.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
STARCAT_NO_UPDATE_CHECK
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablestarcat-app/starcat-cli is public and reachablegithub.com/starcat-app/starcat-cli ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-04github.com/starcat-app/starcat-cli ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubStarcat CLI
中文说明
Preferred install method:
brew tap starcat-app/starcat
brew trust starcat-app/starcat
brew install --cask starcat
Useful links:
- Home and downloads: https://starcat.ink
- Mac App Store: search for Starcat for GitHub
- Public support: https://github.com/starcat-app/Starcat/issues · Release notes: https://starcat.ink/changelog.html
- Starcat App Homebrew tap: https://github.com/starcat-app/homebrew-starcat
- CLI / MCP: starcat-cli / Homebrew tap
- AI Agent Skill: https://github.com/starcat-app/starcat-skill
- Browser plugins: Chrome / Safari
- Launcher integrations: Alfred / uTools / Raycast
- Documentation: https://github.com/starcat-app/starcat-docs
- Website source: https://github.com/starcat-app/starcat-site
- Localization: https://github.com/starcat-app/starcat-localization
Self-hostable support APIs:
- starcat-sharing-api
- starcat-trending-api
- starcat-weekly-api
- starcat-wiki-api
- starcat-recommend-api
- starcat-discovery-api
starcat is the cross-platform command-line client for Starcat and a stdio MCP server for AI agents such as Codex and Claude Code.
The CLI never reads the Starcat database directly and does not duplicate application business logic. Every read and write goes through Starcat MCP tools, so permissions, dry-run behavior, Pro entitlement checks, and audit logging remain enforced by the Starcat app.
Supported platforms
- macOS:
arm64,amd64 - Linux:
arm64,amd64 - Windows:
amd64
The Starcat app still runs on macOS. The CLI may run on the same Mac or connect from a trusted LAN, Tailscale, or WireGuard device.
Install
Homebrew
brew tap starcat-app/starcat-cli
brew install starcat
The tap repository is starcat-app/homebrew-starcat-cli; the installed command is starcat.
macOS and Linux install script
curl -fsSL https://github.com/starcat-app/starcat-cli/releases/latest/download/install.sh | sh
The default destination is ~/.local/bin/starcat. Override it when needed:
curl -fsSL https://github.com/starcat-app/starcat-cli/releases/latest/download/install.sh \
| STARCAT_INSTALL_DIR=/custom/bin sh
Windows PowerShell
irm https://github.com/starcat-app/starcat-cli/releases/latest/download/install.ps1 | iex
The default destination is $HOME\.local\bin\starcat.exe.
Every installer reports platform detection, download, checksum verification, and installation progress. Assets come from GitHub Releases and are verified against checksums.txt before installation. The completion message includes PATH guidance, pairing steps, and common commands.
Pair with Starcat
In Starcat, open Settings > MCP Service, start the service, and click Copy Pairing Command. Paste the complete command into the target device's terminal and press Enter, then approve the device in Starcat:
starcat pair "starcat-pair://connect?..."
starcat doctor
For manual entry, run starcat pair, paste the URI, and press Enter. Pairing commands expire after five minutes, can only be redeemed once, and still require approval inside Starcat. Long-lived device credentials are stored in macOS Keychain, Windows Credential Manager, or Linux Secret Service.
Configure an MCP client
After pairing, configure the AI agent with a user-level MCP server:
{
"command": "/absolute/path/to/starcat",
"args": ["mcp"]
}
starcat mcp bridges line-delimited JSON-RPC between stdio and Starcat MCP Streamable HTTP. Protocol messages are written only to stdout; diagnostics are written to stderr.
Commands
starcat help
starcat capabilities
starcat stats
starcat stats ai --range 30d
starcat stats knowledge
starcat search "local RAG" --source all --limit 30
starcat repo search "local RAG" --scope starred --limit 20
starcat repo context owner/repo
starcat repo readme owner/repo
starcat repo summary owner/repo
starcat tags list
starcat search is the stable JSON entry point for external launchers such as
Alfred. It calls starcat.global_search_repos, merges Starcat local FTS and
GitHub Search results, preserves source labels, and returns a safe open_url.
The existing starcat repo search command remains local-only unless semantic
search is explicitly requested.
Launcher adapters should validate against the shared fixtures in
contracts/global-search. This directory
is the v1 contract source for schema compatibility, partial-provider warnings,
empty results, and stable error codes.
help, version, pair, unpair, doctor, update, and all stats commands use terminal-friendly output. They intentionally have no JSON-output flag because agents receive structured results through starcat mcp. Existing data commands such as capabilities, repo, and tags write JSON directly.
Statistics are read-only local aggregates. starcat stats shows the common Star, knowledge-base, AI token, and RAG chunk counts; stats ai supports --range, --feature, --provider, and --model; stats knowledge shows source coverage and index health.
Write operations are dry-run by default and require --apply to persist changes:
printf '%s' 'A private note' | starcat repo note set owner/repo
printf '%s' 'A private note' | starcat repo note set owner/repo --apply
starcat repo tags add owner/repo Swift macOS --apply
starcat repo status set owner/repo using --apply
Updates
The CLI checks GitHub Releases at most once every 24 hours and displays an English notice only in an interactive terminal. It never prints update notices in starcat mcp or automated pipelines.
Disable automatic checks:
export STARCAT_NO_UPDATE_CHECK=1
Update a script-installed binary:
starcat update
Homebrew installations remain managed by Homebrew:
brew update
brew upgrade starcat
Security model
- Plaintext HTTP is restricted to loopback addresses.
- Remote connections require TLS 1.3 and the paired SHA-256 certificate fingerprint.
- Each device receives an independent, revocable token.
- Long-lived tokens are never written to command arguments, stdout, logs, or project files.
- Downloaded update archives must match the SHA-256 release manifest.
- Starcat MCP permissions remain the final authorization boundary.
See SECURITY.md for vulnerability reporting and threat-model details.
Development
Requires Go 1.25 or newer. The module pins the release toolchain to Go 1.26.10 or newer so published binaries include the current standard-library security fixes.
go mod verify
go test ./...
go test -race ./...
go vet ./...
go build -o bin/starcat ./cmd/starcat
Release builds inject a semantic version:
go build -ldflags "-X github.com/starcat-app/starcat-cli/internal/mcp.Version=v0.1.0" ./cmd/starcat
scripts/build-all.sh v0.1.0 creates the five platform archives, installers, and checksums.txt under dist/. It does not create tags or publish a release.
Contributing
See CONTRIBUTING.md and CODE_OF_CONDUCT.md.
License
MIT. Binary distributions also include THIRD_PARTY_NOTICES.md.
Starcat MCP questions
Are write operations permanent by default?
No, write operations are dry-run by default and require the --apply flag to persist changes.