Other · Local MCP server
Filevine MCP
Open-source MCP server connecting Claude to Filevine practice management. Built by Oktopeak.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.oktopeak/filevine-mcp- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-05
- Updated
- 2026-05-05
- Publisher
- oktopeak (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/oktopeak) · how
- Repository
- github.com/oktopeak/filevine-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @oktopeak/filevine-mcp | 1.0.1 | stdio |
How to connect Filevine MCP
Filevine MCP runs locally from a Node.js package published to the npm registry: @oktopeak/filevine-mcp version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @oktopeak/filevine-mcp@1.0.1. It reads these environment variables: FILEVINE_CLIENT_ID (required, secret), FILEVINE_CLIENT_SECRET (required, secret), FILEVINE_PAT (required, secret), FILEVINE_REGION and ENCRYPTION_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"filevine-mcp": {
"command": "npx",
"args": [
"-y",
"@oktopeak/filevine-mcp@1.0.1"
],
"env": {
"FILEVINE_CLIENT_ID": "<secret>",
"FILEVINE_CLIENT_SECRET": "<secret>",
"FILEVINE_PAT": "<secret>",
"FILEVINE_REGION": "<value>",
"ENCRYPTION_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from oktopeak (GitHub)
| Server | Runs |
|---|---|
| Clio MCPConnect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing. | Local · stdio |
| IntakeQ MCPIntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write. | Local · stdio |
| Lawmatics MCPConnect Claude to Lawmatics: matters, contacts, pipelines, tasks, forms, custom fields, invoices. | Local · stdio |
| Mycase MCPConnect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| FileSeal Secure SendSend a file to a person as a one-time, encrypted, auto-deleting download link. | Local · stdio |
| fileshareforagents.onlineStorage for AI agents: free public items, or private items paid with credits or USDC (x402). | Local · stdio |
| Filesystem MCPSecure filesystem MCP server for reading, writing, searching, diffing, and patching files. | Local · stdio |
| FileSystem MCP ServerSecure filesystem access for AI agents with configurable directory and file type restrictions. | Local · stdio |
| FilingcheckReal SEC EDGAR filing metrics: margin-of-safety, EPS growth, going-concern flags. | Remote · HTTPLive check: ✓ handshake |
| FilingFirehoseSEC EDGAR filings parsed: 8-K body-text classification, 13D activist tagging, S-3 ATM detection. | Remote · HTTPLive check: ✓ handshake |
| FilingsSEC-signed profiles for 8,000+ US public companies from EDGAR filings. Token-efficient. | Remote · HTTPLive check: ✓ handshake |
| FimemoryLocal-first shared memory for AI tools. Your files, encrypted at rest by default; budgeted reads. | Local · stdio |