Log inSubmit server
OctoCounts MCP Server logo

OctoCounts MCP Server

Analyze public GitHub repositories through MCP and inspect cached SLOC breakdowns by language, files, code, comments, and blanks.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install OctoCounts MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "octocounts-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "octocounts"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y octocounts

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

OctoCounts MCP Server MCP server gives MCP clients access to SLOC reports for public GitHub repositories. It analyzes a selected branch, tag, or commit by downloading the repository archive and running tokei, then exposes results that can be compared across repositories. Reports include file, total-line, code, comment, blank, and language counts, with results cached by repository, commit, and tokei version. Reach for it when an agent needs repository-size data without cloning or manually inspecting GitHub language statistics.

Use cases

  • Analyze the SLOC of a public GitHub repository
  • Compare line counts across public repositories
  • Inspect code, comment, blank, and file totals by language
  • Check a repository at a specific branch, tag, or commit

Key features

  • Public GitHub repository SLOC analysis
  • Per-language file and line breakdowns
  • Branch, tag, and commit reference support
  • Cached reports keyed by repository revision and tokei version
  • Queued analysis jobs

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · octocounts (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars19Stargazers on the source repository.
npm downloads7Package downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How OctoCounts MCP Server works

What OctoCounts MCP Server MCP server does

OctoCounts MCP Server MCP server makes OctoCounts repository-size data available to agents and developer assistants through MCP. The underlying service analyzes public GitHub repositories and reports source lines of code (SLOC) by language. Results can include the number of files, total lines, code lines, comment lines, blank lines, and languages found.

This is useful when an agent needs a measurable view of repository size rather than GitHub's language-percentage display. It can support analysis and comparison of public repositories, including checking whether a codebase is relatively small, large, or dominated by a particular language.

How it works

The service resolves a repository reference such as a branch, tag, or commit SHA. It downloads the GitHub archive for that revision instead of cloning the repository, avoiding Git history and reducing the amount of data needed for counting. The archive is then processed with tokei, which produces per-language counts for files, code, comments, blanks, and total lines.

Reports are associated with the repository owner, repository name, resolved commit, and tokei version. This lets repeated requests for the same revision use cached data rather than starting a new count. Analysis jobs are queued so concurrent requests are handled through a job system instead of all running immediately.

Tools and capabilities

OctoCounts MCP Server MCP server is intended for clients that need to retrieve or use OctoCounts SLOC reports.

  • Analyze a public GitHub repository's SLOC.
  • Compare repository line-count results.
  • Inspect counts broken down by programming language.
  • Retrieve file, total-line, code, comment, blank, and language totals.
  • Work against a specific branch, tag, or commit reference.
  • Reuse cached results for an already analyzed commit.

The source project also exposes reports through a web app, browser extension, CLI, GitHub Action, badges, and HTTP API. Those surfaces are part of OctoCounts generally and should not be assumed to be MCP tools unless the MCP documentation confirms the mapping.

Limitations and notes

The documented analysis scope is public GitHub repositories. It also does not provide installation commands, transport details, configuration fields, environment variables, or named MCP client compatibility information.

Counts describe what tokei reports for the selected archive and revision. Results may differ when the branch, tag, or commit changes. Because the cache is tied to a resolved commit and tokei version, a new revision or counting-version change can produce a separate report. Use a pinned commit when reproducibility matters.

The repository is licensed under MIT. The README identifies Rust, Axum, Tokio, SQLx, Postgres, and tokei in the backend stack, but those implementation details do not by themselves define requirements for an MCP client.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about OctoCounts MCP Server

OctoCounts MCP Server is an MCP server that connects AI agents and developer assistants to OctoCounts reports for public GitHub repositories. Its main tools support analyzing repositories and comparing SLOC data, including file, total-line, code, comment, blank, and language-count results.

It identifies the MCP server as one OctoCounts surface, but points to the repository's MCP documentation for implementation details that are not included here.

The description says the MCP server can be used from any MCP client, but it does not name Cursor or provide client-specific setup instructions.

Yes, OctoCounts supports analysis of a specific commit SHA. It resolves branches, tags, and commit references, then associates the cached report with the resulting commit and the tokei version.

It returns SLOC metrics including files, total lines, code lines, comments, blanks, and language counts. The results are broken down by language and are generated by processing a GitHub repository archive with tokei.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOctoCounts MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/octocounts-mcp-server?style=directory)](https://allmcps.com/mcp/octocounts-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/octocounts-mcp-server"><img src="https://allmcps.com/api/badge/octocounts-mcp-server?style=directory" alt="OctoCounts MCP Server on AllMCPs" /></a>