FinishKit MCP server

Read from the package source without running it. The installed server may list more.

• create_projectwrite action

  Create a new FinishKit project by linking a GitHub repository. Note: This requires the FinishKit GitHub App to be installed on the repository first. If the GitHub App is not installed, this tool will direct the user to https://finishkit.app/dashboard to install it and create the project through the web interface. Returns setup instructions with a direct link to the dashboard.

• get_findings

  Retrieve detailed findings from a completed FinishKit scan. Findings include security vulnerabilities, deployment blockers, stability issues, test gaps, and UI problems. Each finding includes the affected file path, line numbers, severity, category, detailed explanation, and suggested fix. Use this after scan_repo completes to get the full list of issues, optionally filtered by category or severit

• get_patches

  Retrieve automatically generated code patches from a completed FinishKit scan. Patches are diff-format code changes that fix detected issues. Each patch includes the affected finding title, the unified diff, application status, and verification status. Use this to see what code changes FinishKit recommends, or to apply fixes to the codebase.

• get_scan_status

  Check the current status of an in-progress FinishKit scan. Returns the scan phase (clone, detect, analyze, patch, verify, pr, finalize), progress percentage, and estimated time remaining. Use this to poll a running scan that was triggered separately, or to check if a previously started scan has completed.

• list_projects

  List all FinishKit projects connected to your account. Each project represents a GitHub repository that has been linked to FinishKit. Returns project IDs, repository names, last scan status, and last scan date. Use this to see which repositories are configured, find project IDs for other API calls, or check when a repository was last scanned.

• scan_repo

  Scan a GitHub repository with FinishKit to detect security vulnerabilities, deployment blockers, stability issues, test coverage gaps, and UI problems. This is the primary tool - it handles the full scan lifecycle: finds the project, triggers a new scan run, polls until completion (typically 2-8 minutes), and returns a comprehensive summary of all findings. Use this when a user wants to check if t

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 182 days ago4/15
• Maintainer identityregistry namespace matches repository owner7/10

FinishKit: common questions

Is FinishKit MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the FinishKit safety report

How do I install FinishKit?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does FinishKit need an API key?

Yes. The registry entry asks for FINISHKIT_API_KEY.

Is FinishKit maintained?

The last commit was 197 days ago (2026-03-30). The latest release is v0.1.0.

What can I use instead of FinishKit?

Servers from other publishers that do the same job: GitHub MCP server, Gk CLI MCP server and Grasp — Code Architecture & Dependency Analysis MCP server. Compare all FinishKit alternatives.