Log inSubmit server
Finish Kit MCP logo

Finish Kit MCP

Scan connected GitHub repositories for security, deployment, stability, testing, and UI issues, then review findings and patches.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Finish Kit MCP

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": {
    "mcp-195": {
      "command": "npx",
      "args": [
        "-y",
        "@finishkit/mcp"
      ]
    }
  }
}

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

Automated check passed— started and listed 9 tools correctly (25d ago).

Overview

Finish Kit MCP MCP server connects AI clients to FinishKit for production-readiness scans of connected GitHub repositories. It can start scans, report progress, filter findings by category or severity, and return unified-diff patches for detected issues. Use it when an agent needs to assess whether an application is ready to ship or synchronize local analysis results with the FinishKit dashboard. Authentication can be completed through a browser activation flow, and setup tools work without an API key.

Use cases

  • Scan a connected GitHub repository before release
  • Review security findings above a chosen severity
  • Inspect generated unified-diff fixes for launch blockers
  • Request stack-specific rules for local analysis
  • Sync local findings to the FinishKit dashboard

Key features

  • GitHub repository production-readiness scans
  • Finding filters by category and severity
  • Scan progress and event access
  • Generated unified-diff patches
  • Framework-specific intelligence packs
  • Dashboard synchronization with deduplication

Tools9

What Finish Kit MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.8k tokens of context

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.

24/24 checks healthy over the last 90d

What it can do

From the 9 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age224 days
Maintainers1

Observed 2026-10-14 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @finishkit/mcp (npm)

Adoption & maintenance

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

npm downloads151Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed9Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Finish Kit MCP works

What Finish Kit MCP MCP server does

Finish Kit MCP MCP server gives supported AI clients access to FinishKit’s production-readiness workflow for GitHub repositories. It evaluates areas including security, deployment, stability, tests, and UI completeness, then exposes prioritized results for an agent to inspect. The main scan operation accepts a repository owner and name, with optional run type and commit selection, and returns a run identifier, finding counts, a summary, and a dashboard URL.

The server is intended for teams that want an AI coding client to check whether a repository is ready to ship. It can also support local analysis workflows by providing stack-specific intelligence packs and accepting findings synchronized back into the FinishKit dashboard.

How it works

A typical workflow starts with scan_repo, which triggers a scan and waits through its lifecycle. Use get_scan_status when progress details are needed. After completion, get_findings returns prioritized issues and can narrow results by category, such as security or deployment, or by minimum severity. get_patches returns generated unified diffs for applicable fixes; applying those patches remains an external action.

Projects must be connected to FinishKit. list_projects shows repositories already available, while create_project returns instructions for connecting another GitHub repository. For local scanning, request_intelligence_pack produces framework- and stack-specific rules, advisories, and prompts. sync_findings records the resulting analysis in the dashboard with deduplication.

Finish Kit MCP MCP server also exposes resources for project data, individual project details, scan findings, and scan event logs. These use finishkit:// URIs and can provide structured context beyond tool responses.

Setup and configuration

Finish Kit MCP MCP server is distributed as the @finishkit/mcp npm package and can be launched with npx -y @finishkit/mcp. The documented login command opens a browser for GitHub or Google sign-in, while the setup command can detect an editor or target Claude Code, Cursor, Windsurf, Codex, or VS Code. Manual MCP configuration uses the FINISHKIT_API_KEY environment variable.

An API key is not required to start the server. Without one, finishkit_setup reports connection status and creates a browser-based activation link. create_project also works without a key.

Tools and capabilities

  • Start baseline, pull-request, or manual-patch scans for a GitHub repository.
  • Track scan phases and percentage completion.
  • Retrieve findings by category, severity, and result limit.
  • Request generated fixes as unified diffs.
  • List connected repositories and obtain connection instructions.
  • Request intelligence packs for JavaScript or TypeScript stacks using npm, pnpm, Yarn, or Bun.
  • Synchronize local findings with project, agent, stack, timing, and summary metadata.
  • Check setup status and obtain activation instructions.

Limitations and notes

The material describes GitHub repositories connected through FinishKit; it does not establish support for arbitrary repository hosts. A scan normally takes approximately two to eight minutes. get_findings requires a completed scan run, and scan-related calls require the relevant run ID. A repository that is not connected must first be linked through the FinishKit dashboard.

The server can start without credentials, but authenticated operations depend on a valid FinishKit connection or API key. The documentation does not state that generated patches are automatically applied, so they should be reviewed and applied through the developer’s normal workflow. Finish Kit MCP MCP server is licensed under MIT.

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 Finish Kit MCP

Finish Kit MCP is an MCP server that connects AI clients to FinishKit and connected GitHub repositories. Its main tools start production-readiness scans, check progress, retrieve categorized findings, return generated unified-diff patches, manage projects, request intelligence packs, and sync local findings to the FinishKit dashboard.

Run `npx -y @finishkit/mcp` through your MCP client configuration. You can also run `npx @finishkit/mcp login` for browser authentication or `npx @finishkit/mcp setup` to configure a supported editor.

Yes, the server starts without an API key. `finishkit_setup` can create a browser-based activation link, and `create_project` can return repository connection instructions without credentials.

Call `scan_repo` with the repository owner and name. The scan returns a run ID and summary; use that ID with `get_scan_status`, `get_findings`, or `get_patches` to follow up.

Related MCP servers

All in Security 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 PreviewFinish Kit MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-195?style=directory)](https://allmcps.com/mcp/mcp-195)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-195"><img src="https://allmcps.com/api/badge/mcp-195?style=directory" alt="Finish Kit MCP on AllMCPs" /></a>