filevine-mcp

MCP server for Filevine — full API coverage for legal case management. Use Filevine from Claude Desktop with natural language.

What you can do

• Projects (Matters) — create, update, archive, manage vitals, custom forms, collections
• Contacts — full CRUD, addresses, emails, phones, project associations
• Tasks — create, assign, complete, pin, snooze, manage by project or user
• Notes — create, pin, comment, tag management
• Documents — CRUD, revisions, lock/unlock, batch upload/download, search, share links
• Folders — organise documents in folder hierarchies
• Billing — billing items, invoices, payments, trust funds, rate schedules
• Project Teams — assign and manage team members per project
• Appointments & Deadlines — schedule and track on matters
• Emails — log email communications to projects
• Webhooks — subscribe to Filevine events for real-time notifications
• Teams — manage organisation teams
• Reference data — project types, document series, classifications, reports

Requirements

• Python 3.10+
• Claude Desktop (or any MCP-compatible client)
• Filevine API credentials (Client ID, Client Secret)
• Filevine region: us, ca, or cjis

Filevine API access: Obtain credentials from your Filevine organisation administrator or developer portal.

Installation

pip install filevine-mcp

Setup

filevine-mcp-setup

This prompts for your Client ID, Client Secret, Org ID, and region, then tests the credentials and saves them to ~/.filevine-mcp/.

Verify:

filevine-mcp-verify

Claude Desktop Configuration

{
  "mcpServers": {
    "filevine": {
      "command": "filevine-mcp"
    }
  }
}

Credential storage

By default credentials are stored in your operating system's native secret store via the cross-platform keyring library:

Secrets are saved under the service name filevine-mcp. Nothing is written to disk in clear text.

File fallback. On a host with no keyring backend (e.g. a headless Linux box without Secret Service), or if you set FILEVINE_MCP_USE_KEYRING=0, credentials fall back to a ~/.filevine-mcp/.env file with 0600 permissions.

Read order. Credentials resolve in the order OS keyring → process environment → .env file. So a rotated secret in the keyring always wins, and a FILEVINE_CLIENT_ID / FILEVINE_CLIENT_SECRET exported in your shell overrides the file fallback without touching the keyring.

Authentication Notes

Filevine uses OAuth 2.0 client credentials flow — no browser authorization required. Tokens are fetched automatically and refreshed when they expire. Three regions are supported with separate API and identity hosts:

Example usage in Claude

"List my open projects"

"Create a task on project 456 — send retainer agreement to client"

"Get the billing vitals for project 789"

"Add a note to project 123 — client called re: mediation date"

"Search documents for 'deposition transcript'"

"List all webhook event types available"

License

MIT