FirmOps

io.firmopsPublished by firmops.ioOfficial publisherv1.0.0Updated Nov 5, 2026

Managed firm-brain MCP for law firms: Clio matters, intake, calendar, and calls over OAuth.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant OAuth-secured access to a law firm's Clio matters, intake, calendar and calls.

What you can do
  • Connect to a managed firm-brain service for law firms.
  • Work with Clio matters and client intake.
  • Reach calendar entries and call records.
  • Access is granted through OAuth rather than local configuration.
When to use it
Useful for law firms already using Clio that want an assistant to look up matters, intake details, calendar items and calls from one managed endpoint, without running a local server.
Requirements
A remote streamable HTTP endpoint at mcp.firmops.io; no packages or environment variables are declared. OAuth authentication is required, so a FirmOps account and authorization through the provider are needed, plus network access.
Before you install
The server handles confidential legal practice data (matters, intake, calls) and is reached over OAuth, so review which scopes and firm data the assistant may read or change. Tool-level behavior is not documented in the supplied material, so confirm whether any actions write or modify Clio records before use.

Installation

In SourceWeft

  1. Open FirmOps in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.firmops%2Ffirmops/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "firmops": {
      "type": "http",
      "url": "https://mcp.firmops.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.