Superpractice

com.superpracticePublished by superpractice.comOfficial publisherv1.0.0Updated Oct 24, 2026

Marketing and practice analytics for law firms: leads, meetings, attribution, ads, SEO, pipeline.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Gives an assistant access to a law firm's marketing and practice analytics: leads, meetings, attribution, ads, SEO and pipeline.

What you can do
Superpractice is a remote MCP server for law firms' marketing and practice analytics. Its description lists leads, meetings, attribution, ads, SEO and pipeline as the areas it covers. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when a law firm wants an assistant to work with its marketing and intake performance data, such as lead sources, meeting activity, ad and SEO results, or pipeline.
Requirements
A remote server reached at app.superpractice.com over streamable HTTP. OAuth authentication is required, so a Superpractice account with the appropriate access is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a firm's marketing and practice data, which may include client or lead information. The manifest does not list the tools, so what the assistant can read or change is not documented here; check the provider's permissions before connecting.

Installation

In SourceWeft

  1. Open Superpractice 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/com.superpractice%2Fsuperpractice/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": {
    "superpractice": {
      "type": "http",
      "url": "https://app.superpractice.com/api/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.0LatestSep 16, 2026

Score

67% 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
  • 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.