Fossick MCP Server

Find libraries, discover gems, search code patterns, and read real production code — across 200M+ repos, PyPI, and npm.. That is what the fossick mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Fossick gives your AI agent seven read-only tools to prospect across all of GitHub, PyPI, and npm, covering the full discovery loop end-to-end:

• Built for the discovery workflow. — Tools follow the natural shape: find candidate → drill into it → read the API → see how others use it. Hint-chained next-step suggestions keep your agent on rails through the whole loop
• Drill into any public repo without cloning. — Browse remote repo trees with depth + glob filters, read any file at any branch/tag/commit, and run real AST-based symbol search to goto-definition for any class, function, or type — all on remote GitHub
• Multi-query search with smart ranking. — search_repos accepts a list of phrasings in one call and applies composite relevance ranking that prioritizes literal match over raw popularity — surfaces the 500-star gem that beats the 50,000-star incumbent
• Rate-limit aware. — Tracks GitHub's Search and Core API buckets separately, sleeps on exhaustion, retries with exponential backoff
• Zero config for gh users. — Already have the GitHub CLI authenticated? Nothing to configure
• Plays well with others. — Read-only, idempotent, safe to auto-approve. Pair Fossick with github-mcp-server when you also need to act on your own repos (issues, PRs, Actions)

Getting it running

Installation goes through your MCP client rather than a global install: point it at fossick-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 6 tools. What each one is for:

• Authentication — 1. GH_TOKEN, GITHUB_TOKEN, or GITHUB_PERSONAL_ACCESS_TOKEN env vars 2. gh auth token from the GitHub CLI — **no config
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server
• Test — Live integration tests — hits real GitHub against pinned modelcontextprotocol/python-sdk@v1.14.0:
• Build — Produces dist/fossick_mcp-.tar.gz and the corresponding wheel
• Architecture — See CLAUDE.md for the full architecture tour, key patterns, and the recipe for adding new tools

What it needs from you

Configuration is passed through the environment: GITHUB_TOKEN, GITHUB_PERSONAL_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.11+ - uv

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fossick MCP's toolset — Authentication, Prerequisites, Setup and 3 more — is a fair guide to whether it matches your workflow. It is maintained by lipdog; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.