Can you connect Clio to Claude? Not officially. Clio's own move into outside AI tools went to OpenAI, not Anthropic. Here's where things stand, what the workarounds really involve, and how firms are putting AI to work on their Clio matters today. The short answer. There is no official Clio connector for Claude. As of October 19, 2026, searching Claude's connector directory for "Clio" returns nothing, and Clio hasn't announced one. When Clio did plug into an outside AI tool, it chose OpenAI: on September 17, 2026, Clio released a plugin that brings its Vincent legal AI into Codex. To get Claude reading Clio today, firms install community-built connectors, route through Zapier, or build their own on Clio's API. Each one ends with a chat window that can look things up. Parker takes a different approach: you sign in with Clio, and an AI employee starts turning your matters into finished drafts for attorney review. Where Clio and Claude stand today. | Question | Answer (Oct 2026) | | Official Clio connector in Claude | No. Claude's connector directory has no Clio listing. | | Clio plugin for another AI tool | Yes, for OpenAI. Vincent became a Codex plugin on September 17, 2026, for Vincent and Clio Work customers. | | Clio's own AI | Clio Work, an AI workspace for research, analysis, and drafting, and Vincent, its legal research AI. | | Clio API | Yes. OAuth sign-in. A developer registers an app in Clio's Developer Portal, separately for each Clio region the firm uses. | | Community connectors for Claude | Several open-source projects and a Zapier option. None are made or supported by Clio or Anthropic. | For comparison, Filevine released an official Claude connector in September 2026, and MerusCase has none (here's that story). If Clio or Anthropic announces a connector, Parker'll update this page. What Clio offers instead: Clio Work and Vincent. Clio's answer to "I want AI on my Clio data" is its own product. Clio Work is an AI workspace for legal research, analysis, and strategy that combines Clio's vLex library of more than a billion legal documents with your matter documents, notes, and contacts. In April 2026, Clio added agentic capabilities that let it carry out multi-step tasks from one instruction, and began selling Clio Work on its own, without a Clio Manage subscription. If your biggest need is legal research grounded in case law, Clio Work and Vincent are serious tools. The question for most plaintiff firms is different: who handles the recurring casework and operations that pile up across Clio, the inbox, Slack, and shared drives? That's the gap a chat connector won't close, and the one Parker was built for. What the workarounds actually involve. If you still want Claude itself reading your Clio matters, there are three routes. All three cost more than they first appear to. * Open-source connectors. Someone at your firm registers a developer app in Clio, installs community code on each computer or server that will use it, and keeps it working through Clio and Claude updates. When it breaks, there's no vendor to call. * Zapier. Easier to set up, but it adds another company between your client files and the AI, and a task-based bill on top of your Claude plan. * Build your own. Full control, plus a software project: authorization, permissions, hosting, rate limits, and a separate app for each Clio region your firm uses. Whichever route you pick, client data now flows through code your firm is responsible for. ABA Formal Opinion 512 asks lawyers to understand how an AI tool handles confidential information before using it, and with a homegrown or community connector, that diligence falls on you. Why "Claude can read my Clio" isn't the finish line. Suppose the connector works perfectly. Your team can now ask Claude about a matter and get a good answer. Here's what still doesn't happen: * Nothing moves when a matter moves. Claude's scheduled tasks run on a timer, not on events. A case changes stage in Clio and no one is drafting the next document until someone notices. * Firm knowledge lives in individual setups. Projects and memory can hold your templates, but each person curates their own, and the way your senior attorney likes a chronology laid out doesn't automatically reach everyone else. * Clio is only part of the file. Correspondence lives in email, documents in Dropbox or Google Drive, and the team talks in Slack. A Clio-only connection sees one slice of the case. * You get an answer, not the work. Someone still has to turn the chat reply into the letter, summary, or discovery response that actually goes out. What Parker does with Clio. Parker is an AI employee for plaintiff firms. It connects to Clio alongside your email, Slack, and document storage, learns how your firm works, and hands back drafts and analysis for your attorneys to review. * Works from your matters. Ask by web chat, email, or Slack: "Parker, summarize where this matter stands and what we still need from the client." Parker pulls the matter, documents, and correspondence it needs. * Starts when a matter changes. During onboarding, Parker can set up triggers so that when a matter reaches a stage, Parker begins drafting the next document and saves it for review. It never sends on its own. * Brings Clio documents to your team. Ask Parker in Slack for a document from a Clio matter and it attaches the file right in the conversation. * Casework across the firm. Discovery responses, complaints, demands, motions, chronologies, case summaries, evaluations, case audits, and mediation preparation. * Learns once, for everyone. Parker starts from the templates and prior work your team trusts, and corrections from one attorney benefit the whole firm. * Your choice of models. Parker supports frontier and open-source AI models, so you get the capability without wiring it together yourself. Claude with a Clio connector vs. Parker. | / | Claude + Clio connector | Parker | | Setup | Register a Clio developer app, install and configure the connector | Sign in to Clio from Parker's Integrations page | | Support | Community maintainers, or your own developer | The Parker team | | Reacts to matter changes | No. Scheduled tasks run on a timer, not on matter events | Yes, with stage-based triggers | | Firm templates and preferences | Set up per person or project | Learned once, shared across the firm | | Sees beyond Clio | Only with more connectors | Email, Slack, Google Workspace, Microsoft 365, Dropbox, and more | | Output | Chat answers | Drafts and analysis ready for attorney review | How to connect Clio to Parker. * Open Integrations in Parker and choose Clio. Start free if you don't have a workspace yet. * Name the account and choose who can use it. Team-only shares the connection with everyone in your Parker workspace. Private limits it to you and the people you invite. * Sign in to Clio and approve access. That's the whole setup. No developer app, no credentials to copy, nothing to install. Its team then helps you load templates and pick the first workflows to hand off. Before you connect any AI to Clio. Ask every vendor, including Parker, the same four questions: * Where is its data processed and stored, and is it kept apart from other firms' data? * Is its data used to train models? * Who controls access, and how do Parker revoke it? * Who reviews the output before it reaches a client, court, or insurer? Parker's answers: each firm gets its own dedicated server, reserved exclusively for that firm. Parker don't train models on your case files, conversations, or firm knowledge. You decide who can use the Clio connection, and your data in Clio stays in Clio. Attorneys review every draft. Read more about security at Parker. Frequently asked questions. Does Clio have an official Claude integration? Is Clio Work the same as Claude? Can I use Clio with ChatGPT or Codex? Who at my firm can use the Clio connection in Parker? Does Parker replace Clio? Sources. * Clio Work vs. Claude vs. Parker: which AI fits your firm? Three different tools for three different problems. What Clio Work, Claude, and Parker are each best at, how they handle Clio data, and which to start with. * Can Claude work on your cases while you sleep? Claude and ChatGPT can now run scheduled tasks with your laptop closed. What that does and doesn't mean for a law firm, and what working overnight should actually look like. * AI medical chronologies: what good looks like, and where they go wrong What a reliable medical chronology includes, where AI versions go wrong, upload tools vs. tools that work in Clio, Filevine, or MerusCase, and how to evaluate any of them. Put AI to work on your Clio matters. Sign in with Clio, bring one workflow you want off your plate, and see what Parker hands back.

Senior software development engineer in test (SDET). About the job: Filevine is a Legal AI company delivering Legal Operating Intelligence for the future of legal work. Grounded in a singular system of truth, Filevine brings together data, documents, workflows, and teams into one unified platform - where modern legal work happens with clarity and consistency. Powered by LOIS, the Legal Operating Intelligence System, Filevine connects context across every matter to transform legal operations from reactive to proactive. LOIS reads, understands, and reasons across your data to surface insight, automate complexity, and give professionals the clarity and confidence to see more, know more, and do more. Fueled by a team of exceptional collaborators and innovators, Filevine's rapid growth has earned AI awards and recognition from Deloitte and Inc. as one of the most innovative and fastest-growing technology companies in the country. Role Summary: Filevine's Telephony team builds the voice communication capabilities that keep our customers connected to the information and people who matter most to their concerns. The platform spans a range of surfaces, from deep backend services and integrations to customer-facing applications and intelligent, AI-driven voice experiences. We are looking for a Senior SDET to own quality across this full breadth. The ideal engineer is equally at home driving rigorous backend and API testing, validating customer-facing applications, and inventing new approaches to test systems that resist conventional, UI-driven automation. This is a backend-leaning, tooling-heavy role for an engineer who wants to solve hard testing problems and raise the quality bar for the entire team, not simply execute existing test plans. Responsibilities. * Design and write test plans and automated test scripts across backend services, APIs, and customer-facing applications * Analyze and improve the scalability, performance, and efficiency of the testing pipeline * Design and implement automated test frameworks * Build solutions to aid in automated and load testing * Responsibly drive complex projects forward to completion * Exercise independent judgment * Make informed recommendations to management * Provide leadership and mentoring to other engineers * Independently identify opportunities for automated testing at different levels (End to End, Integration, UI, etc.) and possible solutions * Communicate frequently, clearly, and effectively with various technical and management audiences on usability, serviceability, and suggested changes Qualifications: * 7+ years working as a software engineer or test automation engineer * Expert in an object oriented language such as C# or Java * Complete understanding of the application development life cycle * Expert knowledge of QA testing techniques and the STLC * Expert experience testing REST web services * Expert at testing backend-heavy services where little or no user interface is available to drive testing * Demonstrated ability to design and build custom test tooling and harnesses for systems that are difficult to exercise through conventional automation, including asynchronous and event-driven services * Practical experience applying GenAI/LLMs to solve engineering productivity, test generation, and analysis challenges * Experience with stress and load testing tools and techniques Nice to have: * Experience testing telephony, VoIP, or other real-time communication systems * Experience testing AI-driven, conversational, or agent-based applications * Familiarity with modern front-end frameworks * Expert understanding of advanced techniques such as stubbing and mocking * Expert understanding of source control systems (GitLab) and CI/CD pipelines * Expert understanding of automated testing frameworks such as Playwright Compensation Information: $160,000 - $185,000 The base salary range represents the low and high end of the salary range for this position. The total compensation package for this position will be determined by each individual's location, qualifications, education, work experience, skills and performance. We believe in the importance of pay equity - the range listed is just one component of Filevine's total compensation package for employees. This position is also eligible for a paid time off policy, as well as a comprehensive benefits package. Cool Company Benefits: - A dynamic, rapidly growing company, focused on helping organizations thrive - Medical, Dental, & Vision Insurance (for full-time employees) - Competitive & Fair Pay - Maternity & paternity leave (for full-time employees) - Short & long-term disability - Opportunity to learn from a dedicated leadership team - Top-of-the-line company swag Communication about this opportunity, or any open role at Filevine, will only come from representatives with email addresses using "filevine.com". Other addresses reaching out are not affiliated with Filevine and should not be responded to. * Eligibility - Appears open to: United States (from the employer's job posting location) * Time zones - New York, Chicago, Denver, Los Angeles * Last verified - today * Compensation - $160K - $185K USD/Year Salary posted | * Category - QA & Testing * Applicants - 65 Company Benefits. | Please let Filevine know you found this opening on Remote Army, with your support we can keep providing you with fresh quality remote jobs. Filevine. Please mention that you come from Remote Army when applying for this job. Don't miss out on new remote jobs! Related Jobs

Filevine integrations for automatic time capture: What law firms should add to their PMS. See how PointOne captures work across emails, documents, meetings, calls, and other applications, then converts it into compliant time entries for review and release into Filevine. Julia Bodet What Filevine manages within the firm Why work performed outside Filevine can still go unrecorded How PointOne creates and assigns time entries How approved entries move into Filevine Why a PMS migration is the right time to improve timekeeping FAQs about PointOne's integration with Filevine 3 minutes read Sep 23, 2026 AI summary. * Filevine manages a firm's cases, matters, documents, workflows, and billing data. * PointOne captures work performed across email, documents, meetings, calls, browsers, and other applications. * PointOne uses AI to assign activity to matters and generate compliant draft time entries. * Attorneys review and approve their entries before releasing them into Filevine. * A migration from ProLaw or another PMS is a practical opportunity to improve timekeeping alongside the firm's broader workflows. What Filevine manages within the firm. Filevine serves as the operational system of record for legal work. Firms can use it to organize matters and case data, manage documents and workflows, track deadlines, and support timekeeping, billing, invoicing, and payments. That centralization gives attorneys and staff a consistent place to manage the lifecycle of a matter. It also gives the billing team structured client, matter, time, and financial data to work with. PointOne does not replace that foundation. It adds an automatic time-capture and billing-compliance layer around it. Why work performed outside Filevine can still go unrecorded. Even with a modern PMS, attorneys still perform a large share of their work elsewhere. They draft in Word, respond in Outlook or Gmail, attend calls and meetings, review PDFs, conduct research in a browser, and move repeatedly between matters throughout the day. If recording that work depends on starting a timer or reconstructing the day later, some activity can still fall through the cracks. Short emails, quick calls, document revisions, and fragmented research sessions are especially easy to overlook. The problem is not where the matter is managed. It is the gap between performing work and recording it accurately. How PointOne creates and assigns time entries. PointOne captures work across the applications attorneys already use, including emails, documents, calendar events, calls, meetings, and browser activity. It then interprets that activity and creates draft time entries by: * Grouping related work into appropriate entries * Assigning the likely client and matter * Drafting a clear billing narrative * Applying relevant task and activity codes * Checking the entry against firm and client billing guidelines Attorneys can inspect the activity behind an entry, make edits, and confirm that the matter, duration, codes, and narrative are correct. Instead of rebuilding the day from memory, they review work that has already been captured and organized. How approved entries move into Filevine. PointOne provides a direct, firm-level integration with Filevine. Once the connection is configured, PointOne can use the firm's Filevine client and matter data when assigning captured activity. Completed entries remain available for review before release. After approval, they move into Filevine so the firm can continue using its established billing process. The resulting workflow is straightforward: Work happens across the attorney's applications | PointOne captures and converts it into compliant time entries | the attorney or reviewer approves the entries | approved time flows into Filevine. Filevine remains the practice-management and billing system. PointOne helps ensure that more of the work feeding that system is captured, properly assigned, and ready to bill. Why a PMS migration is the right time to improve timekeeping. A migration from ProLaw or another practice-management platform already requires the firm to examine its matter data, workflows, permissions, billing rules, and integrations. That makes it a practical time to address timekeeping as well. Moving existing manual habits into a new PMS may preserve the same missed-time problem. Adding automatic time capture during the transition allows the firm to redesign the workflow around review rather than reconstruction. It also lets the implementation team align client and matter data, user access, billing codes, and approval processes before the new system becomes business as usual. For firms moving to Filevine, the result is a more complete billing workflow: Filevine manages the matters and billing data, while PointOne captures the work completed across the rest of the attorney's day. PointOne adds the automatic time-capture and compliance layer that helps firms get more accurate, review-ready time into Filevine - without asking attorneys to change where they work. Your AI-powered firm starts here. FAQs about PointOne's integration with Filevine. Does PointOne replace Filevine's timekeeping features? Can attorneys correct an entry before it reaches Filevine? What happens if a law firm has a customized Filevine environment? Can PointOne capture non-billable work as well as billable time? Do lawyers have to keep PointOne open while they work?