Finch MCP Server

Tavily Search MCP extension for Finch. That is what the finch 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

You work with Finch in natural language. It reads and processes local files you authorize, remembers context across sessions, and extends through mini tools, skills, and MCP integrations. Built on the open source project Pi.

This repository is the public release hub for Finch. It hosts Finch release assets, official extension source code, and the community registries used by the Finch app and community website.

The tools it exposes

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

• mini — tools.json is the English source registry and contains complete extension metadata
• mini-tools.zh — CN.json provides Chinese name and description overrides matched by id

Getting it running

The server ships on npm as @finchtoys/minitools, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Finch's toolset — mini, mini-tools.zh — is a fair guide to whether it matches your workflow. It is maintained by puterjam; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Finch's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.