Most AI assistants disappear when the conversation ends. Finch gives them lasting state — memory that accumulates, agents that keep running, vaults that version knowledge, and workflows that continue after you close the chat.

Why Finch

Install

Always pin the version. Never use @latest.

# One-command installer (detects common MCP clients)
npx -y -p @finchagentic/mcp@4.6.1 finch install

Claude Code

claude mcp add finch -s user -- npx -y -p @finchagentic/mcp@4.6.1 finch-mcp

Cursor / Windsurf / Claude Desktop

{
  "mcpServers": {
    "finch": {
      "command": "npx",
      "args": ["-y", "-p", "@finchagentic/mcp@4.6.1", "finch-mcp"]
    }
  }
}

VS Code

{
  "servers": {
    "finch": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "-p", "@finchagentic/mcp@4.6.1", "finch-mcp"]
    }
  }
}

No LLM API key is required to start — 111 of 116 tools are plain reads/writes/on-chain calls that your MCP client's own model already drives; only 5 (ask_finch, deep_research, and scheduled agent learning) do their own multi-step reasoning server-side and need a key (see Configuration). Tools load on first use.

Quick start

finch doctor          # health check
finch setup           # local vault / memory / providers
finch vault           # inspect local vault
finch orders          # schedule Robinhood Chain DCA / TP-SL order ticks

Try in your MCP client:

remember: I prefer conservative DeFi strategies, max 5% risk
spawn an agent called research-bot to track AI agent news, update it after each session
save this thesis to vault

What you get

116 tools across four pillars:

Coding and research sessions persist the same way: deep_research auto-saves its report to vault and links it to related past reports; code_session_save does the same for coding/debugging sessions (vault_save type=code, versioned per project, auto-linked). Both exist so the next session — yours or another agent's — starts with real context instead of cold.

vault_save and agent_spawn also take an optional workspaceProject - the same named Projects a user organizes their Agents/vault content into on the webapp's Agents page. Pass a name and it's matched case-insensitively or created automatically (list_projects to browse what exists first). Hosted vault only - local-vault mode has no project concept.

Default palette is core (lighter context). Full set:

"env": { "FINCH_TOOLS": "all" }

Fully local

Finch is the runtime. Your LLM is the brain. Your data stays yours.

npx -y -p @finchagentic/mcp@4.6.1 finch setup
# enable local vault (and optional local memory)

Scheduled/cloud features still need an account. Core memory, vault, and public-data tools work offline of Finch cloud.

Configuration

Cost model: almost everything is free to run — the other 110 tools are plain API/RPC calls, and your MCP client's own model (Claude, GPT, whatever's driving the chat) does all the tool-selection reasoning at no cost to Finch. The 5 exceptions above need their own key because their reasoning happens inside the tool call, invisible to your client, and can't be delegated to it. Set exactly one of the four env vars and every tool that needs it will use it automatically.

Guided setup:

npx -y -p @finchagentic/mcp@4.6.1 finch setup

Security

Troubleshooting

Links

MIT License · Finch