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+
• Python MCP SDK >=2.2,<3 (supports the MCP 2026-07-28 protocol)
• 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 through the configured credential store.

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 saved to the keyring use the service name filevine-mcp.

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.

On Windows, the file is stored in the user's profile and protected by Windows' default per-user access rules. On POSIX, files are created with 0600 permissions and writes fail closed if private permissions cannot be established.

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

Approved destination URLs

Set FILEVINE_ALLOWED_DESTINATION_HOSTS in the server environment, for example FILEVINE_ALLOWED_DESTINATION_HOSTS=hooks.firm.example,.integrations.firm.example. Comma-separated exact hosts allow only that host; a leading dot allows the domain and its subdomains. Matching ignores case and trailing dots and normalizes IDNA. An empty or unset list refuses destination URLs before any request. HTTPS, no userinfo, and public literal addresses remain required. This administrator-owned list prevents model-supplied destinations from sending data to arbitrary hosts, including private-address DNS aliases and unapproved redirectors. Approve only hosts whose DNS and redirects the firm trusts; the vendor executes requests later. Tools cannot change this setting.

FILEVINE_REGION and setup accept only us, ca, or cjis. Values are trimmed and lowercased; unknown values fail with an error; they never select a different region. Webhook destinations in fields_json use an explicit set of destination aliases, validated by the same allowlist even inside nested objects and arrays. Unrelated fields such as securityLevel and jurisdiction pass unchanged.