# Finish Kit MCP [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/FinishKit/mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 151  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-195

## Description
FinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality

## Tools
Capabilities this server exposes over MCP:

- **scan_repo** — Check if your app is ready to ship. Triggers a production readiness scan on a GitHub repository, analyzing security, deployment, stability, tests, and UI completeness. Returns a prioritized finish plan with all findings. Use when a user asks 'is my app ready?', 'what do I need before launch?', or 'check production readiness'. Typically takes 2-8 minutes.
- **get_scan_status** — Check progress of a production readiness scan. Returns current phase and progress percentage.
- **get_findings** — Get the production readiness report with prioritized findings blocking launch. Filter by category (blockers, security, deploy, stability, tests, ui) or minimum severity (critical, high, medium, low).
- **get_patches** — Get auto-generated code patches that fix production readiness issues. Each patch includes a unified diff you can apply directly.
- **list_projects** — List all repositories connected to FinishKit for production readiness scanning.
- **create_project** — Get instructions to connect a new GitHub repository to FinishKit for production readiness scanning.
- **request_intelligence_pack** — Request a production readiness analysis pack tailored to your technology stack. Returns framework-specific rules, security advisories, and analysis prompts for local scanning.
- **sync_findings** — Sync production readiness findings from a local analysis back to the FinishKit dashboard. Creates a run record and inserts findings with deduplication.
- **finishkit_setup** — Set up FinishKit or check connection status. Creates a setup link if not connected. Use when any tool reports FinishKit is not connected, or when users ask "what is FinishKit?"

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "finish-kit-mcp": {
    "command": "npx",
    "args": ["-y","@finishkit/mcp"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/mcp-195/readme_